[jira] [Work logged] (BEAM-9203) Programmatically determine if SQL exception is user error, unsupported, or bug
[ https://issues.apache.org/jira/browse/BEAM-9203?focusedWorklogId=381089=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-381089 ] ASF GitHub Bot logged work on BEAM-9203: Author: ASF GitHub Bot Created on: 03/Feb/20 17:04 Start Date: 03/Feb/20 17:04 Worklog Time Spent: 10m Work Description: kennknowles commented on pull request #10699: [BEAM-9203] Clarify exceptions in SQL modules URL: https://github.com/apache/beam/pull/10699 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: 381089) Time Spent: 1h (was: 50m) > Programmatically determine if SQL exception is user error, unsupported, or bug > -- > > Key: BEAM-9203 > URL: https://issues.apache.org/jira/browse/BEAM-9203 > Project: Beam > Issue Type: Improvement > Components: dsl-sql, dsl-sql-zetasql >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Right now there are a lot exceptions thrown by the Calcite SQL dialect and > ZetaSQL dialect of Beam SQL. It is hard to catch just the errors that are > user errors, or just the errors that are unsupported operations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-9203) Programmatically determine if SQL exception is user error, unsupported, or bug
[ https://issues.apache.org/jira/browse/BEAM-9203?focusedWorklogId=380174=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-380174 ] ASF GitHub Bot logged work on BEAM-9203: Author: ASF GitHub Bot Created on: 31/Jan/20 19:14 Start Date: 31/Jan/20 19:14 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #10699: [BEAM-9203] Clarify exceptions in SQL modules URL: https://github.com/apache/beam/pull/10699#issuecomment-580871171 I have rebased and resolved the conflict that came up. Please take another look. 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: 380174) Time Spent: 50m (was: 40m) > Programmatically determine if SQL exception is user error, unsupported, or bug > -- > > Key: BEAM-9203 > URL: https://issues.apache.org/jira/browse/BEAM-9203 > Project: Beam > Issue Type: Improvement > Components: dsl-sql, dsl-sql-zetasql >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Right now there are a lot exceptions thrown by the Calcite SQL dialect and > ZetaSQL dialect of Beam SQL. It is hard to catch just the errors that are > user errors, or just the errors that are unsupported operations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-9203) Programmatically determine if SQL exception is user error, unsupported, or bug
[ https://issues.apache.org/jira/browse/BEAM-9203?focusedWorklogId=379062=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-379062 ] ASF GitHub Bot logged work on BEAM-9203: Author: ASF GitHub Bot Created on: 29/Jan/20 22:33 Start Date: 29/Jan/20 22:33 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #10699: [BEAM-9203] Clarify exceptions in SQL modules URL: https://github.com/apache/beam/pull/10699#issuecomment-579993357 run sql postcommit 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: 379062) Time Spent: 40m (was: 0.5h) > Programmatically determine if SQL exception is user error, unsupported, or bug > -- > > Key: BEAM-9203 > URL: https://issues.apache.org/jira/browse/BEAM-9203 > Project: Beam > Issue Type: Improvement > Components: dsl-sql, dsl-sql-zetasql >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Right now there are a lot exceptions thrown by the Calcite SQL dialect and > ZetaSQL dialect of Beam SQL. It is hard to catch just the errors that are > user errors, or just the errors that are unsupported operations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-9203) Programmatically determine if SQL exception is user error, unsupported, or bug
[ https://issues.apache.org/jira/browse/BEAM-9203?focusedWorklogId=379061=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-379061 ] ASF GitHub Bot logged work on BEAM-9203: Author: ASF GitHub Bot Created on: 29/Jan/20 22:33 Start Date: 29/Jan/20 22:33 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #10699: [BEAM-9203] Clarify exceptions in SQL modules URL: https://github.com/apache/beam/pull/10699#issuecomment-579993273 All fixed up and green. 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: 379061) Time Spent: 0.5h (was: 20m) > Programmatically determine if SQL exception is user error, unsupported, or bug > -- > > Key: BEAM-9203 > URL: https://issues.apache.org/jira/browse/BEAM-9203 > Project: Beam > Issue Type: Improvement > Components: dsl-sql, dsl-sql-zetasql >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Right now there are a lot exceptions thrown by the Calcite SQL dialect and > ZetaSQL dialect of Beam SQL. It is hard to catch just the errors that are > user errors, or just the errors that are unsupported operations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-9203) Programmatically determine if SQL exception is user error, unsupported, or bug
[ https://issues.apache.org/jira/browse/BEAM-9203?focusedWorklogId=378386=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-378386 ] ASF GitHub Bot logged work on BEAM-9203: Author: ASF GitHub Bot Created on: 28/Jan/20 18:20 Start Date: 28/Jan/20 18:20 Worklog Time Spent: 10m Work Description: amaliujia commented on issue #10699: [BEAM-9203] Clarify exceptions in SQL modules URL: https://github.com/apache/beam/pull/10699#issuecomment-579385899 tag @amaliujia so it appears on my pull request list. 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: 378386) Time Spent: 20m (was: 10m) > Programmatically determine if SQL exception is user error, unsupported, or bug > -- > > Key: BEAM-9203 > URL: https://issues.apache.org/jira/browse/BEAM-9203 > Project: Beam > Issue Type: Improvement > Components: dsl-sql, dsl-sql-zetasql >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Right now there are a lot exceptions thrown by the Calcite SQL dialect and > ZetaSQL dialect of Beam SQL. It is hard to catch just the errors that are > user errors, or just the errors that are unsupported operations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-9203) Programmatically determine if SQL exception is user error, unsupported, or bug
[ https://issues.apache.org/jira/browse/BEAM-9203?focusedWorklogId=378012=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-378012 ] ASF GitHub Bot logged work on BEAM-9203: Author: ASF GitHub Bot Created on: 28/Jan/20 02:36 Start Date: 28/Jan/20 02:36 Worklog Time Spent: 10m Work Description: kennknowles commented on pull request #10699: [BEAM-9203] Clarify exceptions in SQL modules URL: https://github.com/apache/beam/pull/10699 This can make it possible to know if it is user error, bad table metadata, unsupported SQL features, or real bug. - InvalidTableException in table providers to show malformed metadata - UnsupportedOperationException when features incomplete Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [x] [**Choose reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and mention them in a comment (`R: @username`). - [x] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue. - [x] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). See the [Contributor Guide](https://beam.apache.org/contribute) for more tips on [how to make review process smoother](https://beam.apache.org/contribute/#make-reviewers-job-easier). Post-Commit Tests Status (on master branch) Lang | SDK | Apex | Dataflow | Flink | Gearpump | Samza | Spark --- | --- | --- | --- | --- | --- | --- | --- Go | [](https://builds.apache.org/job/beam_PostCommit_Go/lastCompletedBuild/) | --- | --- | [](https://builds.apache.org/job/beam_PostCommit_Go_VR_Flink/lastCompletedBuild/) | --- | --- | [](https://builds.apache.org/job/beam_PostCommit_Go_VR_Spark/lastCompletedBuild/) Java | [](https://builds.apache.org/job/beam_PostCommit_Java/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink/lastCompletedBuild/)[](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Batch/lastCompletedBuild/)[](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Streaming/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark/lastCompletedBuild/)[](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Spark_Batch/lastCompletedBuild/)[](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_SparkStructuredStreaming/lastCompletedBuild/) Python | [