[
https://issues.apache.org/jira/browse/FLINK-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969518#comment-14969518
]
ASF GitHub Bot commented on FLINK-2897:
---------------------------------------
GitHub user greghogan opened a pull request:
https://github.com/apache/flink/pull/1290
[FLINK-2897] [runtime] Use distinct initial indices for OutputEmitter
round-robin
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/greghogan/flink
2898_invert_travis_ci_build_order
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1290.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 #1290
----
commit dfb482e14535870c1599895949668e4bc252479f
Author: Greg Hogan <[email protected]>
Date: 2015-10-22T15:12:43Z
[FLINK-2898] [build] Invert Travis CI build order
----
> Use distinct initial indices for OutputEmitter round-robin
> ----------------------------------------------------------
>
> Key: FLINK-2897
> URL: https://issues.apache.org/jira/browse/FLINK-2897
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Runtime
> Affects Versions: 0.10
> Reporter: Greg Hogan
> Assignee: Greg Hogan
>
> Currently, when performing a round-robin partitioning each task will
> sequentially partition starting with partition "1". This is fine in the usual
> case where the number of partitioned objects greatly exceeds the number of
> channels. However, in the case where the number of objects is relatively few
> (each, perhaps, requiring a large computation or access to an external
> system) it would be much better to begin partitioning at distinct indices
> (the task index).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
