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

Posted to issues@flink.apache.org by "Jin Xing (Jira)" <ji...@apache.org> on 2020/12/22 11:18:00 UTC

[jira] [Updated] (FLINK-20716) Pluggable shuffle service public interface IndexedInputGate mixed with Netty shuffle service implementation.

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

Jin Xing updated FLINK-20716:
-----------------------------
    Description: IndexedInputGate provided by pluggable shuffle service as a public interface, and intend to allow user to extend/customize the shuffle-read behavior. Currently its method of IndexedInputGate#getChannel returns InputChannel, which from my understanding binds to Netty shuffle service implementation. Should we keep IndexedInputGate independent ?

> Pluggable shuffle service public interface IndexedInputGate mixed with Netty shuffle service implementation.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-20716
>                 URL: https://issues.apache.org/jira/browse/FLINK-20716
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Jin Xing
>            Priority: Major
>
> IndexedInputGate provided by pluggable shuffle service as a public interface, and intend to allow user to extend/customize the shuffle-read behavior. Currently its method of IndexedInputGate#getChannel returns InputChannel, which from my understanding binds to Netty shuffle service implementation. Should we keep IndexedInputGate independent ?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)