You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "lincoln lee (Jira)" <ji...@apache.org> on 2023/10/10 14:08:00 UTC

[jira] [Updated] (FLINK-33182) Allow metadata columns in NduAnalyzer with ChangelogNormalize

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

lincoln lee updated FLINK-33182:
--------------------------------
    Fix Version/s: 1.19.0

> Allow metadata columns in NduAnalyzer with ChangelogNormalize
> -------------------------------------------------------------
>
>                 Key: FLINK-33182
>                 URL: https://issues.apache.org/jira/browse/FLINK-33182
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Planner
>            Reporter: Timo Walther
>            Assignee: lincoln lee
>            Priority: Major
>             Fix For: 1.19.0
>
>
> Currently, the NduAnalyzer is very strict about metadata columns in updating sources. However, for upsert sources (like Kafka) that contain an incomplete changelog, the planner always adds a ChangelogNormalize node. ChangelogNormalize will make sure that metadata columns can be considered deterministic. So the NduAnalyzer should be satisfied in this case. 



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