Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Redesign strategies #164

Open
chmp opened this issue Apr 13, 2024 · 0 comments
Open

Redesign strategies #164

chmp opened this issue Apr 13, 2024 · 0 comments

Comments

@chmp
Copy link
Owner

chmp commented Apr 13, 2024 •
edited
Loading

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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chmp