[
https://issues.apache.org/jira/browse/FLINK-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549633#comment-15549633
]
ASF GitHub Bot commented on FLINK-4736:
---------------------------------------
GitHub user greghogan opened a pull request:
https://github.com/apache/flink/pull/2601
[FLINK-4736] [core] Don't duplicate fields in Ordering
Duplicate fields should not be appended to an ordering. In an ordering each
subsequent field is only used as a comparison when all prior fields test equal;
therefore, a repeated field cannot contribute to the ordering.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/greghogan/flink
4736_dont_duplicate_fields_in_ordering
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2601.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2601
----
commit 28eda6a6252ad65fb34205bb70e2b079e0a89f02
Author: Greg Hogan <[email protected]>
Date: 2016-10-04T15:37:37Z
[FLINK-4736] [core] Don't duplicate fields in Ordering
Duplicate fields should not be appended to an ordering. In an ordering
each subsequent field is only used as a comparison when all prior fields
test equal; therefore, a repeated field cannot contribute to the
ordering.
----
> Don't duplicate fields in Ordering
> ----------------------------------
>
> Key: FLINK-4736
> URL: https://issues.apache.org/jira/browse/FLINK-4736
> Project: Flink
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
> Priority: Minor
> Fix For: 1.2.0
>
>
> Duplicate fields should not be appended to an ordering. In an ordering each
> subsequent field is only used as a comparison when all prior fields test
> equal; therefore, a repeated field cannot contribute to the ordering.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)