flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4903) Introduce non async future methods
Date Thu, 27 Oct 2016 13:39:58 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15611919#comment-15611919

ASF GitHub Bot commented on FLINK-4903:

Github user tillrohrmann commented on the issue:

    That is true. I'll increase the timeouts to 10s just to be sure. The failing test case
is unrelated. Will merge the PR then. Thanks for the review @uce and @StephanEwen.

> 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

View raw message