[
https://issues.apache.org/jira/browse/CALCITE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768150#comment-17768150
]
Julian Hyde commented on CALCITE-6021:
--------------------------------------
I have a partial fix in
[6021-datetime|https://github.com/julianhyde/calcite/tree/6021-datetime].
The {{lookupOperatorOverloads}} methods in {{ListSqlOperatorTable}} and
{{ReflectiveSqlOperatorTable}} treat syntax inconsistently. (One uses
{{instanceof SqlFunction}}, and another checks {{SqlSyntax.family}}.) That
needs to be fixed. Can you finish the job, [~tanclary]?
> Add CURRENT_DATETIME function (enabled in BigQuery library)
> -----------------------------------------------------------
>
> Key: CALCITE-6021
> URL: https://issues.apache.org/jira/browse/CALCITE-6021
> Project: Calcite
> Issue Type: Bug
> Reporter: Tanner Clary
> Priority: Major
>
> Calcite supports parsing and validation for the CURRENT_DATETIME function
> according to CALCITE-4297 . However a native implementation was never added.
> The docs for the function may be found here:
>
> https://cloud.google.com/bigquery/docs/reference/standard-sql/datetime_functions#current_datetime
> An example:
> {{SELECT CURRENT_DATETIME([timezone])}} should return the current time as a
> {{DATETIME}} (a Calcite TIMESTAMP). There is an optional time zone argument.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
