Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Tue, 10 Feb 2015 09:04:35 +0000 (UTC)
From: "Ufuk Celebi (JIRA)" <jira@apache.org>
To: dev@flink.incubator.apache.org
Message-ID: <JIRA.12773742.1423559065000.311303.1423559075069@Atlassian.JIRA>
In-Reply-To: <JIRA.12773742.1423559065000@Atlassian.JIRA>
References: <JIRA.12773742.1423559065000@Atlassian.JIRA>
 <JIRA.12773742.1423559065360@arcas>
Subject: [jira] [Created] (FLINK-1505) Separate buffer reader and channel
 consumption logic
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ufuk Celebi created FLINK-1505:
----------------------------------

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