You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Sergey Nuyanzin (Jira)" <ji...@apache.org> on 2023/05/11 20:32:00 UTC

[jira] [Resolved] (CALCITE-4554) TIMESTAMP WITH LOCAL TIME ZONE type is not supported in Snapshot and MatchRecognize validation

     [ https://issues.apache.org/jira/browse/CALCITE-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Nuyanzin resolved CALCITE-4554.
--------------------------------------
    Fix Version/s: 1.35.0
       Resolution: Fixed

> 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
>             Fix For: 1.35.0
>
>          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)