You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/22 07:19:00 UTC

[jira] [Updated] (FLINK-11403) Remove ResultPartitionConsumableNotifier from ResultPartition

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

ASF GitHub Bot updated FLINK-11403:
-----------------------------------
    Labels: pull-request-available  (was: )

> Remove ResultPartitionConsumableNotifier from ResultPartition
> -------------------------------------------------------------
>
>                 Key: FLINK-11403
>                 URL: https://issues.apache.org/jira/browse/FLINK-11403
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Network
>            Reporter: zhijiang
>            Assignee: zhijiang
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>
> This is the precondition for introducing pluggable {{ShuffleService}} on TM side.
> In current process of creating {{ResultPartition}}, the {{ResultPartitionConsumableNotifier}} regarded as TM level component has to be passed into the constructor. In order to create {{ResultPartition}} easily from {{ShuffleService}}, the required information should be covered by {{ResultPartitionDeploymentDescriptor}} as much as possible, then we could remove this notifier from the constructor. And it is also reasonable for notifying consumable partition via {{TaskActions}} which is already covered in {{ResultPartition}}.



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