[
https://issues.apache.org/jira/browse/FLINK-20716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Xing updated FLINK-20716:
-----------------------------
Parent: FLINK-22672
Issue Type: Sub-task (was: Bug)
> 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: Sub-task
> Components: Runtime / Coordination
> Reporter: Jin Xing
> Priority: Minor
> Labels: auto-deprioritized-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)
