[
https://issues.apache.org/jira/browse/FLINK-38209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-38209.
--------------------------------
Fix Version/s: 2.2.0
(was: 2.2)
Resolution: Fixed
Fixed in master: cae5fb4d3b6d9e0c10c3539ea4994fc1ad463b70
> Use UniqueKeys instead of Upsertkeys for state management
> ---------------------------------------------------------
>
> Key: FLINK-38209
> URL: https://issues.apache.org/jira/browse/FLINK-38209
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Runtime
> Affects Versions: 2.1
> Reporter: Gustavo de Morais
> Assignee: Gustavo de Morais
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.2.0
>
>
> When creating MultiJoins, we currently use UpsertKeys as the UniqueKeys for
> the inputSideSpecs. Even though that is not wrong since upsertKeys are always
> unique keys, that makes us only use UniqueKeys optimizations for a subset of
> cases when we have unique keys.
> In other words, for joins, we'll often use a state with hasNoUniqueKey even
> though there's a unique key. This is a considerable optimization and we want
> to cange that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
