[ https://issues.apache.org/jira/browse/FLINK-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329061#comment-14329061 ]
ASF GitHub Bot commented on FLINK-1505: --------------------------------------- Github user gyfora commented on the pull request: https://github.com/apache/flink/pull/428#issuecomment-75257236 Thank you! I will try it over the weekend and give you feedback. > Separate buffer reader and channel consumption logic > ---------------------------------------------------- > > Key: FLINK-1505 > URL: https://issues.apache.org/jira/browse/FLINK-1505 > Project: Flink > Issue Type: Improvement > Components: Distributed Runtime > Affects Versions: master > Reporter: Ufuk Celebi > Priority: Minor > > Currently, the hierarchy of readers (f.a.o.runtime.io.network.api) is > bloated. There is no separation between consumption of the input channels and > the buffer readers. > This was not the case up until release-0.8 and has been introduced by me with > intermediate results. I think this was a mistake and we should seperate this > again. flink-streaming is currently the heaviest user of these lower level > APIs and I have received feedback from [~gyfora] to undo this as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)