[
https://issues.apache.org/jira/browse/FLINK-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler updated FLINK-12021:
-------------------------------------
Fix Version/s: (was: 1.8.1)
(was: 1.9.0)
1.8.0
> Let ResultConjunctFuture return future results in same order as futures
> -----------------------------------------------------------------------
>
> Key: FLINK-12021
> URL: https://issues.apache.org/jira/browse/FLINK-12021
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.7.2, 1.8.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.3, 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{ResultConjunctFuture}} should return future results in the same order
> as the futures were specified. The advantage would be that we maintain the
> same output order as the input order if the input has been specified with a
> special ordering.
> This should also fix a current performance regression where we don't maintain
> the topological ordering when deploying tasks. Due to this, we need to make
> an additional result partition lookup which adds additional latency. The
> problem has occurred due to FLINK-10431 which changes the interleaving how
> the slot futures are completed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
