alamb commented on issue #686:
URL:
https://github.com/apache/arrow-datafusion/issues/686#issuecomment-875543176
> Should the current output of to_timestamp(...) default to Timestamp(_,
Some(UTC)) ? This sounds like a yes (and would solve my use case)
While this might be theoretically the best option, I think this would be a
fairly painful change (at least for us in IOx) as our timestamps are
`Timestamp(Nanoseconds, None)`
> to_timestamp(....) can be extended to add a second argument to accept
different time zones, or None (not sure how to specify None if the default is
UTC, per item 1)
Perhaps `to_timestamp('....', NULL)` could work
> Or, simplify everything and have the timestamp types not have timezone,
but just if they are UTC or local (similar to Parquet).
I am actually a fan of this direction -- I am fairly sure the use of a
Timezone that is something other than `None` will not work well in Arrow /
DataFusion (Because I tried using `Timestamp(.., Some("UTC")` in IOx and basic
query stuff didn't work
I think it would keep things simpler to convert timestamps on the edge (aka
if it was "local time" convert to UTC prior to putting into DataFusion) and
then have all the processing machinery deal with UTC timestamps only
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
