[
https://issues.apache.org/jira/browse/FLINK-32466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738076#comment-17738076
]
Timo Walther commented on FLINK-32466:
--------------------------------------
This bugs affects many functions not only CONCAT. In the PR I went through all
functions and synchronized the strategy with the runtime implementation.
> Invalid input strategy for many functions which allows BINARY strings
> ---------------------------------------------------------------------
>
> Key: FLINK-32466
> URL: https://issues.apache.org/jira/browse/FLINK-32466
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
> Labels: pull-request-available
>
> "string" in SQL terms covers both character strings and binary strings. The
> author of CONCAT might not have known this. In any case, the code gen instead
> of the validator fails when executing:
> {code}
> TableEnvironment t =
> TableEnvironment.create(EnvironmentSettings.inStreamingMode());
> t.createTemporaryView("t", t.fromValues(lit(new byte[] {97})));
> t.executeSql("SELECT CONCAT(f0, '-magic') FROM t").print();
> {code}
> As future work, we should also allow binary strings.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
