omus commented on issue #367:
URL: https://github.com/apache/arrow-julia/issues/367#issuecomment-1371473881
> it naively seems like `Timestamp{U}(timezone::String)` would be a better
representation on the Julia front. also unsure how often Arrow.jl internally
might rely on propagating knowledge about arrow table schemas purely via the
Julia "type domain" vs. the Julia "value domain", but I guess that also factors
in as well
This was also what I was thinking when I started looking into this problem.
The challenge is that the time zone information is only stored as metadata in
arrow as seen here:
https://github.com/apache/arrow-julia/blob/2d29402afeaa67aab6c4747f470ab1fc99c69136/src/eltypes.jl#L278-L284
As this function only has access to the type information we'd have to do
some major internal refactoring make this approach work.
> i think part of the point is that we maybe CAN support this even with the
current type arrangement (unless i'm missing something), we'd just have to deal
with union types appropriately in a lot of places
We can store a column of `ZonedDateTime`s using several time zones but from
my understanding just not as the internal arrow timestamp type. Such a column
would need special handling for cross-language interoperability. That's
definitely something that we could make a Julia specific feature but I'm not
seeing a need for that functionality at this time.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
