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

Yanquan Lv resolved FLINK-40240.
--------------------------------
    Fix Version/s: cdc-3.7.0
         Assignee: Mao Jiayi
       Resolution: Fixed

Merged in master via fdacb41de9d1a3df587f3adec74eac6e1f42e016.

> Support TRY_CAST, IFNULL and NULLIF in YAML Transform
> -----------------------------------------------------
>
>                 Key: FLINK-40240
>                 URL: https://issues.apache.org/jira/browse/FLINK-40240
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>            Reporter: Mao Jiayi
>            Assignee: Mao Jiayi
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: cdc-3.7.0
>
>
> Flink CDC YAML Transform currently supports {{CAST}}, {{COALESCE}}, {{IF}}, 
> and {{CASE}}, but common Flink SQL functions {{TRY_CAST}}, {{IFNULL}}, and 
> {{NULLIF}} cannot be used consistently. {{TRY_CAST}} and {{IFNULL}} are 
> unavailable, while {{NULLIF}} can be parsed but does not have complete 
> validation and runtime support.
> This prevents users from safely handling malformed source values with 
> {{TRY_CAST}} and requires verbose alternative expressions for common NULL 
> handling. It also creates an inconsistency between Flink SQL and YAML 
> Transform expressions.
> h2. Expected Behavior
> The three functions should be available in both projection and filter 
> expressions with Flink SQL-compatible behavior. {{TRY_CAST}} should return 
> {{NULL}} for malformed data on supported conversion paths without changing 
> existing {{CAST}} behavior, while unsupported conversion paths should still 
> be rejected. {{IFNULL}} and {{NULLIF}} should follow Flink SQL value, type 
> inference, and nullability semantics.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to