[jira] [Updated] (FLINK-36095) KeyedLookupJoinWrapper should shuffle by input upsertKey instead of join key to avoid changelog disordering

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

> KeyedLookupJoinWrapper should shuffle by input upsertKey instead of join key to avoid changelog disordering
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-36095
>                 URL: https://issues.apache.org/jira/browse/FLINK-36095
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Planner
>    Affects Versions: 1.20.0
>            Reporter: lincoln lee
>            Assignee: lincoln lee
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>
> If user encounter the NDU issue caused by a lookup join and enable the {{TRY_RESOLVE}} mode ( https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/concepts/determinism/#33-how-to-eliminate-the-impact-of-non-deterministic-update-in-streaming ), the current KeyedLookupJoinWrapper implementation use the join key as the shuffle key, this may lead to changelog disordering issue. It should be fixed to use input upsertKey(or the complete row if upsertKey is empty) instead of join key.



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