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

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

                Author: ASF GitHub Bot
            Created on: 09/Oct/19 02:52
            Start Date: 09/Oct/19 02:52
    Worklog Time Spent: 10m 
      Work Description: kennknowles commented on issue #9306: [BEAM-7939] 
ZetaSQL dialect documentation
URL: https://github.com/apache/beam/pull/9306#issuecomment-539798907
 
 
   Well, some BQ folks have tweeted that ZetaSQL is the SQL used by BQ...
   
   But it is true that ZetaSQL has many knobs and BQ SQL represents one 
configuration. BQ SQL also does not include our streaming extensions, while 
Beam SQL's ZetaSQL Dialect does not support a lot of BQ SQL. And Beam ZetaSQL 
users may choose a different configuration of ZetaSQL than BQ, for example to 
match Spanner or some future user of ZetaSQL more closely.
   
   So I'm with Cyrus on this one - I like calling it "ZetaSQL dialect".
 
----------------------------------------------------------------
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: 325454)
    Time Spent: 1.5h  (was: 1h 20m)

> Document ZetaSQL dialect in Beam SQL
> ------------------------------------
>
>                 Key: BEAM-7939
>                 URL: https://issues.apache.org/jira/browse/BEAM-7939
>             Project: Beam
>          Issue Type: Improvement
>          Components: website
>            Reporter: Cyrus Maden
>            Assignee: Cyrus Maden
>            Priority: Major
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Blocked by BEAM-7832. ZetaSQL dialect source will be merged from #9210.



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

Reply via email to