[jira] [Commented] (CALCITE-4313) Date functions CURRENT_* have type different from documentation

["Julian Hyde (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209074#comment-17209074 ] 

Julian Hyde commented on CALCITE-4313:
--------------------------------------

I suspect that the documented behavior is correct and the actual behavior is wrong. Can you please check the SQL standard for what is the standard behavior?

Changing the type of {{CURRENT_TIMESTAMP}}, in particular, from {{TIMESTAMP}} to {{TIMESTAMP WITH TIME ZONE}} will be disruptive. Stream processing systems such as Flink and Beam use it heavily. We will need to consult with them.

> Date functions CURRENT_* have type different from documentation
> ---------------------------------------------------------------
>
>                 Key: CALCITE-4313
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4313
>             Project: Calcite
>          Issue Type: Bug
>    Affects Versions: 1.26.0
>            Reporter: Nils Braun
>            Priority: Minor
>
> The return types of the {{CURRENT_TIME}}, {{CURRENT_DATE}} and {{CURRENT_TIMESTAMP}} operations set in the SqlStdOperatorTable.java (e.g. [here|#L1882]) is different from the [documentation|https://calcite.apache.org/docs/reference.html#datetime-functions]: they are missing the {{_WITH_LOCAL_TIMEZONE}}.
>  I am not an expert, but I think changing them to {{TIME_WITH_LOCAL_TIME_ZONE}} will already do the trick. I am happy to do a PR, if this is really the only thing to do.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)