[
https://issues.apache.org/jira/browse/BEAM-9178?focusedWorklogId=376433&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-376433
]
ASF GitHub Bot logged work on BEAM-9178:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/20 18:53
Start Date: 23/Jan/20 18:53
Worklog Time Spent: 10m
Work Description: apilloud commented on issue #10634: [BEAM-9178] Support
all ZetaSQL TIMESTAMP functions
URL: https://github.com/apache/beam/pull/10634#issuecomment-577822265
On breaking this up: There are a few cleanups (ImmutableList.of fixes,
renaming `TimeStamp` to `Timestamp`) and 73eaef8 `Fix
unparseFunctionsUsingInterval()` that can be pulled into their own PRs and go
in immediately, those look to be about 25% of this change.
I think also be worth pulling the `BeamZetaSqlDateTimePart` stuff (in
67ef67d `Support EXTRACT and TIMESTAMP_TRUNC function`) into a separate change.
We want to eventually support `BeamCalcRel` when possible, this introduces
quite a few regressions that I expect will be controversial.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 376433)
Remaining Estimate: 0h
Time Spent: 10m
> Support ZetaSQL TIMESTAMP functions in BeamSQL
> ----------------------------------------------
>
> Key: BEAM-9178
> URL: https://issues.apache.org/jira/browse/BEAM-9178
> Project: Beam
> Issue Type: New Feature
> Components: dsl-sql-zetasql
> Reporter: Yueyang Qiu
> Assignee: Yueyang Qiu
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Support *all* TIMESTAMP functions defined in ZetaSQL (BigQuery Standard SQL).
> See the full list of functions below:
> [https://cloud.google.com/bigquery/docs/reference/standard-sql/timestamp_functions]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)