[ 
https://issues.apache.org/jira/browse/BEAM-10219?focusedWorklogId=451338&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-451338
 ]

ASF GitHub Bot logged work on BEAM-10219:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Jun/20 23:47
            Start Date: 25/Jun/20 23:47
    Worklog Time Spent: 10m 
      Work Description: robinyqiu commented on pull request #12054:
URL: https://github.com/apache/beam/pull/12054#issuecomment-649871710


   This 
(https://github.com/robinyqiu/beam/commit/06c49a15ba36f23cf3dac54669d5d3fa1f5873c2)
 should fix the precision issue with TIME literal. Please patch it to your PR.
   
   The default ZetaSQL analyzer setup supports microsecond precision (if wants 
nanoseconds you need to set an language option). I believe it's enough for us 
to support microsecond precision. Other system like BigQuery also support 
microsecond.


----------------------------------------------------------------
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: 451338)
    Time Spent: 4h 10m  (was: 4h)

> Support ZetaSQL TIME functions in BeamSQL
> -----------------------------------------
>
>                 Key: BEAM-10219
>                 URL: https://issues.apache.org/jira/browse/BEAM-10219
>             Project: Beam
>          Issue Type: New Feature
>          Components: dsl-sql-zetasql
>            Reporter: Robin Qiu
>            Assignee: Zijie Song
>            Priority: P2
>          Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> Support *all* TIME functions defined in ZetaSQL (BigQuery Standard SQL). See 
> the list of functions below:
> [https://github.com/google/zetasql/blob/master/docs/time_functions.md]



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

Reply via email to