gowerc commented on issue #45751:
URL: https://github.com/apache/arrow/issues/45751#issuecomment-2717193958
Hi @kou thank you for the reply,
> You need to convert it by yourself or we may want to add a new compute
kernel for it.
Apologies I am confused, from the documentation I thought that was the exact
purpose of the `local_timestamp()` computation ? In particular from the docs:
> local_timestamp function converts UTC-relative timestamps to local
“timezone-naive” timestamps. The timezone is taken from the timezone metadata
of the input timestamps.
At least the implication of that from the the way its written is that it is
performing the following calculation (which is what I am looking for):
$$
time_{local} = time_{utc} + offset(timezone)
$$
I should also note for ~99% of cases I've tested so far the
`local_timestamp` function appears to be working as I was hoping / expecting, I
just found this one example where it is not performing as expected.
> BTW, why do you want to get offset-ed seconds?
I am trying to write a small CLI tool that converts parquet data to XPT
format; XPT format however has no support for timezones so how to correctly
store timestamp data is dependent on the use case; some users prefer to store
the data as timezone-naive whilst others (myself included) prefer to just store
the UTC-relative timestamps. To this end I am just providing an option for the
user to choose.
--
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
