[
https://issues.apache.org/jira/browse/FLINK-38069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18011602#comment-18011602
]
Sergey Nuyanzin commented on FLINK-38069:
-----------------------------------------
Merged as
[a356421ded64dc95a7c274e25663e977c9af9dfa|https://github.com/apache/flink/commit/a356421ded64dc95a7c274e25663e977c9af9dfa]
> The nullability of function ENCODE return type differs in Table API and SQL
> ---------------------------------------------------------------------------
>
> Key: FLINK-38069
> URL: https://issues.apache.org/jira/browse/FLINK-38069
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Reporter: dylanhz
> Assignee: dylanhz
> Priority: Major
> Labels: pull-request-available
> Attachments: Snipaste_2025-07-09_11-28-33.png
>
>
> The definition of return type nullability is different in
> `BuiltInFunctionDefinitions#ENCODE` and `FlinkSqlOperatorTable#ENCODE`. The
> same issue applies to DECODE.
> The test in the attached image will pass, clearly the nullability differs in
> Table API and SQL.
> I think we should unify them to enforce nullable return types. And there may
> exist similar diffs in other functions, though I haven't checked yet.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
