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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/09/26 15:05:00 UTC

[jira] [Updated] (FLINK-38445) Create test plans to validate upsert keys

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

ASF GitHub Bot updated FLINK-38445:
-----------------------------------
    Labels: pull-request-available  (was: )

> Create test plans to validate upsert keys
> -----------------------------------------
>
>                 Key: FLINK-38445
>                 URL: https://issues.apache.org/jira/browse/FLINK-38445
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Planner
>    Affects Versions: 2.1.0
>            Reporter: Gustavo de Morais
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.2.0
>
>
> Right now, if there's any issues in the getUpsertKeys logic for MultiJoin, tests won't always catch it. That's because results are still correctly calculated for tests but with a different underlying, less efficient, plan. We want to close that gap adding some test plans to make sure the Sink isn't a SinkMaterialize.



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