[FLINK-3935] Invalid check of key and ordering fields in PartitionNode

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.1.0
• Component/s: API / DataSet
• Assignee: Fabian Hueske
• Reporter: Fabian Hueske
• Created: 19/May/16 12:10
• Updated: 28/Feb/19 14:30
• Resolved: 19/May/16 20:27

Description

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.