[
https://issues.apache.org/jira/browse/BEAM-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022619#comment-17022619
]
Andrew Pilloud commented on BEAM-9182:
--------------------------------------
Thanks for opening. There are two classes to this issue:
# Unparse issues (For example "NULL = TRUE" instead of "TRUE IS NULL"). This
is a visible regression affecting Beam unit tests, I am working on fixing now.
# Query Parameters passing NULL where a NULL literal wouldn't be supported.
This will affect query parameters and currently affects our internal compliance
tests. There are a number of similar issues (for example large number literals
that can be passed through as parameters but not as a parsed literal). The most
complete fix would be to plumb parameters through to ZetaSQLCalcRel rather than
turning them into literals.
> Support NULL parameter in BeamZetaSqlCalcRel
> --------------------------------------------
>
> Key: BEAM-9182
> URL: https://issues.apache.org/jira/browse/BEAM-9182
> Project: Beam
> Issue Type: Improvement
> Components: dsl-sql-zetasql
> Reporter: Yueyang Qiu
> Assignee: Yueyang Qiu
> Priority: Major
>
> After we migrate to BeamZetaSqlCalcRel, query parameters that are NULL values
> will stop working. I believe we need to fix this issue soon in order to make
> query parameters work end to end.
> cc: [~apilloud] [~ibzib] [~kenn]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
