[
https://issues.apache.org/jira/browse/CALCITE-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721902#comment-17721902
]
Sergey Nuyanzin commented on CALCITE-4554:
------------------------------------------
Merged as
[bf8e1142c8635823a45117261c836c95a3994668|https://github.com/apache/calcite/commit/bf8e1142c8635823a45117261c836c95a3994668]
> TIMESTAMP WITH LOCAL TIME ZONE type is not supported in Snapshot and
> MatchRecognize validation
> -----------------------------------------------------------------------------------------------
>
> Key: CALCITE-4554
> URL: https://issues.apache.org/jira/browse/CALCITE-4554
> Project: Calcite
> Issue Type: Improvement
> Reporter: Leonard Xu
> Assignee: Sergey Nuyanzin
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When I plan to support *TIMESTAMP WITH LOCAL TIME ZONE* type in Flink
> project , I found only *TIMESTAMP* is supported in system period type of
> *Snapshot* node and first orderBy column type of *MatchRecognize* node in
> Calcite. So I have to override the class
> _org.apache.calcite.sql.validate.SqlValidatorImpl_ to skip the validate
> logic.
> Both *TIMESTAMP* and *TIMESTAMP WITH LOCAL TIME ZONE* belong to
> *SqlTypeFamily.TIMESTAMP*, Could we also support *TIMESTAMP WITH LOCAL TIME
> ZONE* in these situations?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
