serde_arrow
serde_arrow copied to clipboard
Redesign strategies
Current strategies:
- InconsistentTypes
- UtcStrAsDate64
- NaiveStrAsDate64
- TupleAsStruct
- MapAsStruct
- UnknownVariant
Potential strategies (for temporal types):
- Temporal resolution:
Unit(Seconds),Unit(Milliseconds),Unit(Microseconds),Unit(Nanoseconds) - Serialization preference:
Prefer(Str),Prefer(Int) -
Timezone(Naive),Timezone(Utc)
Q: still required?
Currently the temporal resolution and timezone of the Arrow datatype is used, e.g., Timestamp(Seconds, ...). Only Date64 requires special treatment. Keep the current design and make changes in resolution / timezone responsibility of the user?