[
https://issues.apache.org/jira/browse/ARROW-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361918#comment-17361918
]
Rok Mihevc edited comment on ARROW-13033 at 6/11/21, 5:33 PM:
--------------------------------------------------------------
int64 would make per row timezone "normalization" easier. But maybe there's
something else I'm missing here.
was (Author: rokm):
int64 would also enable per row timezone "normalization" but maybe there's
something else I'm missing.
> [C++] Kernel to localize naive timestamps to a timezone (preserving
> clock-time)
> -------------------------------------------------------------------------------
>
> Key: ARROW-13033
> URL: https://issues.apache.org/jira/browse/ARROW-13033
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Joris Van den Bossche
> Priority: Major
>
> Given a tz-naive timestamp, "localize" would interpret that timestamp as
> local in a given timezone, and return a tz-aware timestamp keeping the same
> "clock time" (the same year/month/day/hour/etc in the printed
> representation). Under the hood this converts the timestamp value from that
> timezone to UTC, since tz-aware timestamps are stored as UTC.
> References:
> [tz_localize|https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DatetimeIndex.tz_localize.html]
> in pandas, or
> [force_tz|https://lubridate.tidyverse.org/reference/force_tz.html] in R's
> lubridate package
> This will (eventually) also have to deal with ambiguous or non-existing times.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
