[
https://issues.apache.org/jira/browse/CALCITE-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608450#comment-17608450
]
Julian Hyde commented on CALCITE-5269:
--------------------------------------
I added a note in {{big-query.iq}} why the BigQuery results contained "UTC"
(they are BigQuery TIMESTAMP values, i.e. instants) but the Calcite results do
not (they are Calcite TIMESTAMP values, i.e. local times). I'll merge shortly.
When I merge CALCITE-5155, {{DATE_TRUNC}} will no longer have a list of time
units hard-coded in the parser (e.g. {{YEAR}}, {{MONTH}}, {{DATE}}) but will
allow user-defined time frames and time units that are invalid for dates (e.g.
{{MINUTE}}) will be caught in the validator, not the parser. There will be
conflicts but we can resolve them.
> Implement BigQuery TIME_TRUNC and TIMESTAMP_TRUNC functions
> -----------------------------------------------------------
>
> Key: CALCITE-5269
> URL: https://issues.apache.org/jira/browse/CALCITE-5269
> Project: Calcite
> Issue Type: Sub-task
> Reporter: TJ Banghart
> Assignee: TJ Banghart
> Priority: Major
>
> Implement missing BigQuery functions for:
> * TIME_TRUNC
> * TIMESTAMP_TRUNC
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
