[jira] [Commented] (FLINK-38417) Ensure attribute ordering when managing join attributes in JoinKeyExtractor

["Sergey Nuyanzin (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-38417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18073396#comment-18073396 ] 

Sergey Nuyanzin commented on FLINK-38417:
-----------------------------------------

2.1: [f64c549aeea2ab019eee1381824ddc40142c4d72|https://github.com/apache/flink/commit/f64c549aeea2ab019eee1381824ddc40142c4d72]

> 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)