[
https://issues.apache.org/jira/browse/BEAM-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020690#comment-17020690
]
Kirill Kozlov commented on BEAM-9169:
-------------------------------------
Yes, we might be able to fix this by specifying what needs escaping and what
does not (or using a different escaping method). Not sure how to achieve that,
but I will look into it.
> 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
>
> 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)
