[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=326668=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-326668 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 11/Oct/19 02:15 Start Date: 11/Oct/19 02:15 Worklog Time Spent: 10m Work Description: kennknowles commented on pull request #9306: [BEAM-7939] ZetaSQL dialect documentation URL: https://github.com/apache/beam/pull/9306 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 326668) Time Spent: 2h 50m (was: 2h 40m) > 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: 2h 50m > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[
https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=326667=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-326667
]
ASF GitHub Bot logged work on BEAM-7939:
Author: ASF GitHub Bot
Created on: 11/Oct/19 02:14
Start Date: 11/Oct/19 02:14
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #9306:
[BEAM-7939] ZetaSQL dialect documentation
URL: https://github.com/apache/beam/pull/9306#discussion_r333802917
##
File path: website/src/documentation/dsls/sql/zetasql/overview.md
##
@@ -0,0 +1,67 @@
+---
+layout: section
+title: "Beam ZetaSQL overview"
+section_menu: section-menu/sdks.html
+permalink: /documentation/dsls/sql/zetasql/overview/
+---
+
+# Beam ZetaSQL overview
+Beam SQL supports a varient of the
[ZetaSQL](https://github.com/google/zetasql) language. ZetaSQL is similar to
the language in BigQuery's SQL framework. This Beam SQL dialect is especially
useful in pipelines that [write to or read from BigQuery
tables](https://beam.apache.org/releases/javadoc/current/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.html).
+
+Beam SQL has additional extensions leveraging Beam’s unified batch/streaming
model and processing complex data types. You can use these extensions with all
Beam SQL dialects, including Beam ZetaSQL.
+
+## Query syntax
+Query statements scan tables or expressions and return the computed result
rows. For more information about query statements in Beam ZetaSQL, see the
[Query syntax]({{ site.baseurl
+}}/documentation/dsls/sql/zetasql/query-syntax) reference and [Function call
rules]({{ site.baseurl
+}}/documentation/dsls/sql/zetasql/syntax).
+
+## Lexical structure
+A Beam SQL statement comprises a series of tokens. For more information about
tokens in Beam ZetaSQL, see the [Lexical structure]({{ site.baseurl
+}}/documentation/dsls/sql/zetasql/lexical) reference.
+
+## Data types
+Beam SQL supports standard SQL scalar data types as well as extensions
including arrays, maps, and nested rows. For more information about scalar data
in Beam ZetaSQL, see the [Data types]({{ site.baseurl
}}/documentation/dsls/sql/zetasql/data-types) reference.
+
+## Functions and operators
+The following table summarizes the [ZetaSQL functions and
operators](https://github.com/google/zetasql/blob/master/docs/functions-and-operators.md)
supported by Beam ZetaSQL.
+
+ Operators and functionsBeam ZetaSQL support
+ https://github.com/google/zetasql/blob/master/docs/conversion_rules.md;>Type
conversionYes
+ https://github.com/google/zetasql/blob/master/docs/aggregate_functions.md;>Aggregate
functionsSee Beam SQL aggregate
functions
Review comment:
Since "Beam SQL" is ambiguous and maybe also redundant, maybe just "See
aggregate functions", etc. The context makes clear that it is ZetaSQL.
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 326667)
Time Spent: 2h 40m (was: 2.5h)
> 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: 2h 40m
> 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=326468=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-326468 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 10/Oct/19 17:28 Start Date: 10/Oct/19 17:28 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-540689878 > What about "Beam Calcite SQL" versus "Beam Calcite" I like it. Adds a bit more clarity. Done. 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 326468) Time Spent: 2.5h (was: 2h 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: 2.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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325908=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325908 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 09/Oct/19 20:43 Start Date: 09/Oct/19 20:43 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-540186088 What about "Beam Calcite SQL" versus "Beam Calcite" 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325908) Time Spent: 2h 20m (was: 2h 10m) > 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: 2h 20m > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325906=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325906 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 09/Oct/19 20:42 Start Date: 09/Oct/19 20:42 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-540185595 Yea. If Calcite had a pithy name for their SQL dialect separate from the planner, that would be quite helpful. 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325906) Time Spent: 2h 10m (was: 2h) > 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: 2h 10m > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325839=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325839 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 09/Oct/19 17:38 Start Date: 09/Oct/19 17:38 Worklog Time Spent: 10m Work Description: apilloud commented on issue #9306: [BEAM-7939] ZetaSQL dialect documentation URL: https://github.com/apache/beam/pull/9306#issuecomment-540108809 Beam ZetaSQL still uses Calcite for a bunch of things, which adds to the confusion. I think this is a good improvement. 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325839) Time Spent: 2h (was: 1h 50m) > 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: 2h > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325801=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325801 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 09/Oct/19 16:20 Start Date: 09/Oct/19 16:20 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-540076471 > My high level comment is this: I find the titles "Beam SQL lexical structure (Calcite)" and "Beam SQL Lexical Structure (ZetaSQL)" a bit confusing. I would rather lead with the dialect on the titles for those pages. I'm not sure what would improve it, but "Beam Calcite SQL Lexical structure" and "Beam ZetaSQL Lexical Structure" are a little better (but not nice on the eyes). > > Ditto "Beam SQL operators for ZetaSQL" where I would rather say "Operators (Beam ZetaSQL)" or "Operators in Beam ZetaSQL" or "ZetaSQL operators supported by Beam ZetaSQL" or some such. > > If I summarize the above into a single rule, it would be that once you are talking about a dialect, don't use the term "Beam SQL" any more. SGTM. I like "Beam Calcite" and "Beam ZetaSQL" as shorthands. Will implement this accordingly 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325801) Time Spent: 1h 50m (was: 1h 40m) > 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: 1h 50m > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325456=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325456 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 09/Oct/19 02:56 Start Date: 09/Oct/19 02:56 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-539799833 My high level comment is this: I find the titles "Beam SQL lexical structure (Calcite)" and "Beam SQL Lexical Structure (ZetaSQL)" a bit confusing. I would rather lead with the dialect on the titles for those pages. I'm not sure what would improve it, but "Beam Calcite SQL Lexical structure" and "Beam ZetaSQL Lexical Structure" are a little better (but not nice on the eyes). Ditto "Beam SQL operators for ZetaSQL" where I would rather say "Operators (Beam ZetaSQL)" or "Operators in Beam ZetaSQL" or "ZetaSQL operators supported by Beam ZetaSQL" or some such. If I summarize the above into a single rule, it would be that once you are talking about a dialect, don't use the term "Beam SQL" any more. 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325456) Time Spent: 1h 40m (was: 1.5h) > 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: 1h 40m > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325454=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: us...@infra.apache.org 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325317=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325317 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 08/Oct/19 20:36 Start Date: 08/Oct/19 20:36 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-539693272 Staging links: http://apache-beam-website-pull-requests.storage.googleapis.com/9306/documentation/dsls/sql/overview/index.html http://apache-beam-website-pull-requests.storage.googleapis.com/9306/documentation/dsls/sql/zetasql/overview/index.html 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325317) Time Spent: 1h 20m (was: 1h 10m) > 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: 1h 20m > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325311=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325311 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 08/Oct/19 20:24 Start Date: 08/Oct/19 20:24 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 (using the closed-source name may lead to some legal/trademark roadblocks) - The supported components in Beam SQL are more similar to Dataflow SQL, which is itself a ZetaSQL dialect (unlike BQ SQL, which is similar to but not exactly a ZetaSQL dialect; see below) - BQ Standard SQL is similar to ZetaSQL but (AFAIK) not based on the actual ZetaSQL framework, so using a name like BQ Standard SQL in Beam could misrepresent BQ Standard SQL as a 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325311) Time Spent: 1h 10m (was: 1h) > 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: 1h 10m > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325309=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325309 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 08/Oct/19 20:19 Start Date: 08/Oct/19 20:19 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 (using the closed-source name may lead to some legal/trademark roadblocks) - The supported components in Beam SQL are more similar to Dataflow SQL, which is itself a ZetaSQL dialect (unlike BQ SQL, which is similar to but not exactly a ZetaSQL dialect) - BQ Standard SQL is similar to ZetaSQL but (AFAIK) not based on the actual ZetaSQL framework, so using a name like BQ Standard SQL in Beam could misrepresent BQ Standard SQL as a 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325309) Time Spent: 1h (was: 50m) > 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: 1h > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325291=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325291 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 08/Oct/19 19:31 Start Date: 08/Oct/19 19:31 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 (using the closed-source name may lead to some legal/trademark roadblocks) - The supported components in Beam SQL are more similar to Dataflow SQL, which is itself a ZetaSQL dialect (unlike BQ SQL, which is similar to but not exactly a ZetaSQL dialect) - 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325291) Time Spent: 50m (was: 40m) > 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: 50m > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325289=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325289 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 08/Oct/19 19:30 Start Date: 08/Oct/19 19:30 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 (using the closed-source name may lead to some legal/trademark roadblocks) - 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325289) Time Spent: 40m (was: 0.5h) > 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: 40m > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325287=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: us...@infra.apache.org 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325284=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325284 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 08/Oct/19 19:26 Start Date: 08/Oct/19 19:26 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) 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325284) Time Spent: 20m (was: 10m) > 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: 20m > 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)
[jira] [Work logged] (BEAM-7939) Document ZetaSQL dialect in Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-7939?focusedWorklogId=325283=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325283 ] ASF GitHub Bot logged work on BEAM-7939: Author: ASF GitHub Bot Created on: 08/Oct/19 19:21 Start Date: 08/Oct/19 19:21 Worklog Time Spent: 10m Work Description: apilloud commented on issue #9306: [BEAM-7939] ZetaSQL dialect documentation URL: https://github.com/apache/beam/pull/9306#issuecomment-539663000 High level question: Do we actually want the user facing name to be ZetaSQL dialect? Would Big Query Standard SQL dialect be more appropriate? 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 325283) Remaining Estimate: 0h Time Spent: 10m > 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: 10m > 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)
