You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/07/23 22:10:00 UTC

[jira] [Closed] (FLINK-9909) Remove cancellation of input futures from ConjunctFutures

     [ https://issues.apache.org/jira/browse/FLINK-9909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-9909.
--------------------------------
    Resolution: Fixed

Fixed via
master: 9afda733a90a72be75ced9567452c6a7a5e3dc8c
1.6.0: 234356772ee480e2a331f7aaf0f7f4654a3423d5
1.5.2: a695e6b5eb1a1be6176c358eb1345d2277586b1b

> Remove cancellation of input futures from ConjunctFutures
> ---------------------------------------------------------
>
>                 Key: FLINK-9909
>                 URL: https://issues.apache.org/jira/browse/FLINK-9909
>             Project: Flink
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.5.1, 1.6.0, 1.7.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.2, 1.6.0
>
>
> With FLINK-8749, we introduced that a {{ConjunctFutures}} cancels all of its input futures if it is cancelled. This has, however, some unpleasant side effects since a all of the cancelled future's completing callbacks won't be called. Since this can lead to subtle bugs like in FLINK-9908, I would propose to remove this feature and require the user to do the cancellation of input futures explicitly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)