[
https://issues.apache.org/jira/browse/FLINK-38209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo de Morais updated FLINK-38209:
--------------------------------------
Release Note:
This is considerable optimization and an breaking change for the
StreamingMultiJoinOperator.
As noted in the release notes, the operator was launched in an experimental
state for Flink 2.1 since we're working on relevant optimizations that could be
breaking changes.
> 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
>
>
> 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)
