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] [Updated] (FLINK-12630) Refactor abstract InputGate to general interface
Date Mon, 27 May 2019 08:26:00 GMT

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

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

> Refactor abstract InputGate to general interface
> ------------------------------------------------
>                 Key: FLINK-12630
>                 URL: https://issues.apache.org/jira/browse/FLINK-12630
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Network
>            Reporter: zhijiang
>            Assignee: zhijiang
>            Priority: Minor
>              Labels: pull-request-available
> `InputGate` is currently defined as an abstract class which extracts the common codes
for checking data availability for subclasses `SingleInputGate` and `UnionInputGate`, but
it might bring limits for further extending `InputGate` implementations in shuffle service
> `SingleInputGate` is created from shuffle service so it belongs to the scope of shuffle
service, while `UnionInputGate` is a wrapper of some `SingleInputGate`s so it should be in
the task/processor stack.
> In order to make a new `InputGate` implementation from another new shuffle service could
be directly pitched in, we should define a more clean `InputGate` interface to decouple the
implementation of checking data available logic. In detail we could define the `isAvailable`
method in `InputGate` interface and extract the current implementation as a separate class
`FutureBasedAvailability` which could still be extent and reused for both `SingleInputGate`
and `UnionInputGate`.

This message was sent by Atlassian JIRA

View raw message