[ 
https://issues.apache.org/jira/browse/FLINK-20716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327451#comment-17327451
 ] 

Flink Jira Bot commented on FLINK-20716:
----------------------------------------

This major issue is unassigned and itself and all of its Sub-Tasks have not 
been updated for 30 days. So, it has been labeled "stale-major". If this ticket 
is indeed "major", please either assign yourself or give an update. Afterwards, 
please remove the label. In 7 days the issue will be deprioritized.

> 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
>          Components: Runtime / Coordination
>            Reporter: Jin Xing
>            Priority: Major
>              Labels: stale-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)

Reply via email to