[
https://issues.apache.org/jira/browse/FLINK-38417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-38417.
--------------------------------
Resolution: Fixed
Fixed in master: 04e6437dd4d06b59b3f87651e2043559f3df827e
> Ensure attribute ordering when managing join attributes in JoinKeyExtractor
> ---------------------------------------------------------------------------
>
> Key: FLINK-38417
> URL: https://issues.apache.org/jira/browse/FLINK-38417
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Affects Versions: 2.1.0
> Reporter: Gustavo de Morais
> Assignee: Gustavo de Morais
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.2.0
>
>
> The MultiJoin has a JoinKeyExtractor helper that derives keys from
> AttributeRef mappings in the joinAttributeMap. It describes how attributes
> from different inputs are equated via equi-join * conditions.
> The methods present in the JoinKeyExtractor should always return rows for the
> join conditions and commonJoinKey in the same order so we have stable a
> joinKey for state access and key selector for routing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
