You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2016/05/19 20:28:12 UTC

[jira] [Closed] (FLINK-3935) Invalid check of key and ordering fields in PartitionNode

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

Fabian Hueske closed FLINK-3935.
--------------------------------
    Resolution: Fixed

Fixed with 853a5359eb76a987f3fee33065b34051c2fa6094

> Invalid check of key and ordering fields in PartitionNode
> ---------------------------------------------------------
>
>                 Key: FLINK-3935
>                 URL: https://issues.apache.org/jira/browse/FLINK-3935
>             Project: Flink
>          Issue Type: Bug
>          Components: Optimizer
>    Affects Versions: 1.1.0
>            Reporter: Fabian Hueske
>            Assignee: Fabian Hueske
>             Fix For: 1.1.0
>
>
> {{PartitionNode}} checks for range partitioning that partition keys and the fields of the ordering are identical. However the check is not correctly implemented because {{PartitionNode}} holds the partition keys as an unordered {{FieldSet}} which is compared against an ordered {{FieldList}} provided by the {{Ordering}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)