[
https://issues.apache.org/jira/browse/BEAM-9179?focusedWorklogId=379474&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-379474
]
ASF GitHub Bot logged work on BEAM-9179:
----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Jan/20 16:46
Start Date: 30/Jan/20 16:46
Worklog Time Spent: 10m
Work Description: robinyqiu commented on issue #10715: [BEAM-9179]
Cleanup ZetaSQLQueryPlanner and ExpressionConverter code
URL: https://github.com/apache/beam/pull/10715#issuecomment-580345706
Hi @ibzib could you help with triggering precommit tests and merging the PR?
----------------------------------------------------------------
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: 379474)
Remaining Estimate: 0h
Time Spent: 10m
> Simplify types in Beam ZetaSQL
> ------------------------------
>
> Key: BEAM-9179
> URL: https://issues.apache.org/jira/browse/BEAM-9179
> Project: Beam
> Issue Type: Improvement
> Components: dsl-sql-zetasql
> Reporter: Yueyang Qiu
> Assignee: Yueyang Qiu
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, how types work in Beam ZetaSQL is very confusing: code that does
> type conversion between Calcite/Beam/ZetaSQL type systems are everywhere and
> is likely to be not consistent. In addition, the recent migration to
> BeamZetaSqlCalcRel makes the situation even worse: it adds another layer for
> type conversion and makes a lot of code (for making ZetaSQL functions
> manually) obsolete. This makes debugging and supporting new features very
> hard. A few examples:
> * Support new ZetaSQL types (e.g. DATE/TIME/DATETIME)
> * Fix the long-standing precision & timezone issue of TIMESTMAP type
> * Support BeamSQL query parameters
> Therefore, I propose we work on the following items to make the story of Beam
> ZetaSQL type clearer:
> * Define a clear mapping between Calcite/Beam/ZetaSQL types and values
> * Refactor the codebase to move all type conversion code to a single source
> of truth
> * Add thorough testing for it
> * Remove obsolete code that is added to make functions work before
> BeamZetaSqlCalcRel
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
