[
https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325287&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325287
]
ASF GitHub Bot logged work on BEAM-7939:
----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Oct/19 19:29
Start Date: 08/Oct/19 19:29
Worklog Time Spent: 10m
Work Description: soyrice commented on issue #9306: [BEAM-7939] ZetaSQL
dialect documentation
URL: https://github.com/apache/beam/pull/9306#issuecomment-539665140
> High level question: Do we actually want the user facing name to be
ZetaSQL dialect? Would Big Query Standard SQL dialect be more appropriate?
I like the idea here - renaming to more accurately reflect the intended use
case. But these are some points I'd say in favor of the ZetaSQL name:
- ZetaSQL is open source whereas BigQuery is a closed-source, Google product
- The supported components in Beam SQL are more similar to Dataflow SQL,
which is itself a ZetaSQL dialect (unlike BQ SQL)
- BQ standard SQL is itself more or less another ZetaSQL dialect, so using a
name like BQ Standard SQL in Beam shrouds the underlying SQL framework (since
the dialect in Beam SQL is based off ZetaSQL directly, not the intermediate BQ
standard SQ)
----------------------------------------------------------------
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: 325287)
Time Spent: 0.5h (was: 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: 0.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)