[
https://issues.apache.org/jira/browse/FLINK-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604655#comment-15604655
]
ASF GitHub Bot commented on FLINK-4903:
---------------------------------------
GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/2689
[FLINK-4903] [futures] Introduce synchronous future operations
The synchronous future operations are executed by the thread which adds the
operation
if the future is already completed or by the thread executing the last
operation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink syncFutures
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2689.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 #2689
----
commit a29d458d689259b017015947c114dee026ffcbe8
Author: Till Rohrmann <[email protected]>
Date: 2016-10-25T08:31:53Z
[FLINK-4903] [futures] Introduce synchronous future operations
The synchronous future operations are executed by the thread which adds the
operation
if the future is already completed or by the thread executing the last
operation.
----
> Introduce non async future methods
> ----------------------------------
>
> Key: FLINK-4903
> URL: https://issues.apache.org/jira/browse/FLINK-4903
> Project: Flink
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
>
> Currently, Flink's {{Futures}} support only async methods. This means that
> each chained operation is executed potentially by a different thread. In some
> cases this is not necessary and the context switches inflict additional
> costs. Therefore, I propose to add non async methods to the {{Futures}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
