You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2015/02/23 10:25:11 UTC

[jira] [Resolved] (FLINK-1505) Separate buffer reader and channel consumption logic

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

Ufuk Celebi resolved FLINK-1505.
--------------------------------
    Resolution: Implemented

Implemented in 5232c56

> 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)