[
https://issues.apache.org/jira/browse/ARROW-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544476#comment-15544476
]
Greg Rahn commented on ARROW-315:
---------------------------------
IMHO an important clarification with timestamp is to agree that while the
serialization format may be based of a unix time/UTC offset, technically the
value has no time zone information (e.g. timestamp without time zone). This is
means that no matter what the client or server timezone is set to, the value
remains the same -- it behaves the same way write/read would work for a string
representing a given timestamp.
> Finalize timestamp type
> -----------------------
>
> Key: ARROW-315
> URL: https://issues.apache.org/jira/browse/ARROW-315
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Format
> Reporter: Julien Le Dem
> Assignee: Julien Le Dem
>
> support int64 UNIX timestamps with a particular resolution.
> Parquet supports timestamp millis and micros (no nanos)
> https://github.com/apache/parquet-format/blob/master/LogicalTypes.md#datetime-types
> currently Arrow timestamps have a timezone field.
> https://github.com/apache/arrow/blob/master/format/Message.fbs#L67
> proposal to change timestamp as follows:
> - remove "timestamp" field and say it's UTC
> - add unit field (MICROS | MILLIS)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
