[
https://issues.apache.org/jira/browse/FLINK-40151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18120497#comment-18120497
]
Xiqian Yu commented on FLINK-40151:
-----------------------------------
Merged into master via 85b83fc0444c9f6762839c187d17785ffc69bb71.
> Support missing YAML Transform predicates and nullable BOOLEAN logical
> evaluation
> ---------------------------------------------------------------------------------
>
> Key: FLINK-40151
> URL: https://issues.apache.org/jira/browse/FLINK-40151
> Project: Flink
> Issue Type: Improvement
> Components: Flink CDC
> Reporter: Mao Jiayi
> Assignee: Mao Jiayi
> Priority: Major
> Labels: pull-request-available
>
> CDC YAML Transform supports SQL-like expressions, but some predicates and
> nullable BOOLEAN logical expressions are not handled consistently with Flink
> SQL.
> Some predicates that are valid in Flink SQL are currently unsupported in YAML
> Transform, such as IS UNKNOWN, IS DISTINCT FROM, LIKE ... ESCAPE, and SIMILAR
> TO. In addition, logical expressions involving nullable BOOLEAN values may
> fail at runtime when the operand is NULL, instead of producing the expected
> SQL UNKNOWN result.
> This issue focuses on:
> - AND, OR, NOT with nullable BOOLEAN operands
> - IS TRUE / IS NOT TRUE
> - IS FALSE / IS NOT FALSE
> - IS UNKNOWN / IS NOT UNKNOWN
> - IS DISTINCT FROM / IS NOT DISTINCT FROM
> - LIKE ... ESCAPE
> - SIMILAR TO / NOT SIMILAR TO
> UNKNOWN should be represented as null in projection results. In filter
> expressions, only TRUE should pass; FALSE and UNKNOWN should not pass.
> Changes to comparison operators, BETWEEN, IN, and the existing two-argument
> LIKE / NOT LIKE behavior are out of scope for this issue and should be
> handled separately.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
