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/24 22:00:00 UTC

[jira] [Resolved] (BEAM-9169) Extra character introduced during Calcite unparsing

     [ https://issues.apache.org/jira/browse/BEAM-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirill Kozlov resolved BEAM-9169.
---------------------------------
    Fix Version/s: 2.20.0
       Resolution: Fixed

> Extra character introduced during Calcite unparsing
> ---------------------------------------------------
>
>                 Key: BEAM-9169
>                 URL: https://issues.apache.org/jira/browse/BEAM-9169
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql-zetasql
>            Reporter: Yueyang Qiu
>            Assignee: Kirill Kozlov
>            Priority: Minor
>             Fix For: 2.20.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> When I am testing query string
> {code:java}
> "SELECT STRING(TIMESTAMP \"2008-12-25 15:30:00\", \"America/Los_Angeles\")"{code}
> on BeamZetaSqlCalcRel I found that the second string parameter to the function is unparsed to
> {code:java}
> America\/Los_Angeles{code}
> (note an extra backslash character is added).
> This breaks the ZetaSQL evaluator with error
> {code:java}
> Syntax error: Illegal escape sequence: \/{code}
> From what I can see now this character is introduced during the Calcite unparsing step.



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