[
https://issues.apache.org/jira/browse/CALCITE-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129530#comment-16129530
]
Jesus Camacho Rodriguez commented on CALCITE-1947:
--------------------------------------------------
[~julianhyde], could you review this one?
https://github.com/apache/calcite/pull/519
I would like to make sure I have touched all the right parts and I did not miss
anything. We will need to extend Avatica in a follow-up, thus I changed the
DruidAdapterIT tests that were reading the 'timestamp with timezone' column
accordingly with a cast (at least for the time being). Once Avatica is extended
and version consumed by Calcite bumped up, this restriction does not need to
exist anymore.
Another pending item is the extension of the SQL parser, etc.
However, this patch should be enough to allow systems such as Hive consume /
use the timestamp with timezone type.
> Add time/timestamp with time zone types to optimizer
> ----------------------------------------------------
>
> Key: CALCITE-1947
> URL: https://issues.apache.org/jira/browse/CALCITE-1947
> Project: Calcite
> Issue Type: New Feature
> Components: core
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Fix For: 1.14.0
>
>
> Implementation would be similar to PostgreSQL (the {{time/timestamp with
> timezone}} types do not store the timezone) and conversion from/to
> timezone-less types follows similar semantics.
> https://www.postgresql.org/docs/9.6/static/functions-datetime.html
> This would also allow us to integrate easily with Hive and Druid, which
> follow similar storage models/semantics for timestamp with timezone.
> Follow-up work will be needed to introduce these new types in Avatica and
> extend Calcite SQL parser.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
