[
https://issues.apache.org/jira/browse/ORC-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410592#comment-16410592
]
Jesus Camacho Rodriguez commented on ORC-189:
---------------------------------------------
[~rdblue], I think there is a bit of confusion around this, in fact the Hive
issue referenced here is not related to ORC itself.
- Timestamp with local time zone does not require to store a zone offset. From
Hive, data is indeed converted to UTC and then stored. Hence, timestamp and
timestamp with local time zone can be represented by ORC using same format. In
Hive, when column of timestamp with local time zone type is shown, the
displacement is applied depending on the session time zone (HIVE-16614).
- Druid currently uses timestamp with local time zone to represent its
timestamp column when it is queried by Hive (Druid does not store the timezone
for the timestamp column), but previously it was using timestamp type. In
HIVE-18729 we were discussing how to support both.
- {{Timestamp with time zone}} is a different type where we would store the
zone offset itself and it is currently not supported by Hive.
- To add to the confusion, Postgres calls {{timestamp with time zone}} what
Oracle calls {{timestamp with local time zone}} (if I remember correctly).
> Add timestamp with timezone
> ---------------------------
>
> Key: ORC-189
> URL: https://issues.apache.org/jira/browse/ORC-189
> Project: ORC
> Issue Type: New Feature
> Reporter: Owen O'Malley
> Priority: Major
>
> Hive is adding a timestamp with timezone. We need to figure out the
> corresponding changes to ORC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
