You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kirill Kozlov (Jira)" <ji...@apache.org> on 2020/01/14 20:52:00 UTC

[jira] [Comment Edited] (BEAM-9027) [SQL] ZetaSQL unparsing should produce valid result

    [ https://issues.apache.org/jira/browse/BEAM-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010124#comment-17010124 ] 

Kirill Kozlov edited comment on BEAM-9027 at 1/14/20 8:51 PM:
--------------------------------------------------------------

Brief update on this issue.

Following unparsing errors have been fixed:
 * Calcite cannot unparse RexNode back to bytes literal
 * Calcite cannot unparse some floating point literals correctly
 * Calcite cannot unparse some string literals correctly

Other issues from the initial list (INTERVAL and CAST) still need to be fixed.


was (Author: kirillkozlov):
Brief update on this issue.

Following unparsing error have been fixed:
 * Calcite cannot unparse RexNode back to bytes literal
 * Calcite cannot unparse some floating point literals correctly
 * Calcite cannot unparse some string literals correctly

Other issues from the initial list (INTERVAL and CAST) still need to be fixed.

> [SQL] ZetaSQL unparsing should produce valid result
> ---------------------------------------------------
>
>                 Key: BEAM-9027
>                 URL: https://issues.apache.org/jira/browse/BEAM-9027
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql-zetasql
>            Reporter: Kirill Kozlov
>            Assignee: Kirill Kozlov
>            Priority: Major
>          Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> * ZetaSQL does not recognize keyword INTERVAL
>  * Calcite cannot unparse RexNode back to bytes literal
>  * Calcite cannot unparse some floating point literals correctly
>  * Calcite cannot unparse some string literals correctly
>  * Calcite cannot unparse types correctly for CAST function



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