Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
From: uce <git@git.apache.org>
To: issues@flink.incubator.apache.org
Reply-To: issues@flink.incubator.apache.org
Message-ID: <git-pr-2690-flink@git.apache.org>
Subject: [GitHub] flink pull request #2690: [FLINK-4894] [network] Don't request buffer after ...
Content-Type: text/plain
Date: Tue, 25 Oct 2016 12:43:01 +0000 (UTC)
archived-at: Tue, 25 Oct 2016 16:44:05 -0000

GitHub user uce opened a pull request:

    https://github.com/apache/flink/pull/2690

    [FLINK-4894] [network] Don't request buffer after writing to partition

    After emitting a record via the RecordWriter, we eagerly requested a new buffer for the next emit on that channel (although it's not clear that we will immediately need it). With this change, we request that buffer lazily when an emit call requires it.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/uce/flink 4894-late_request_buffer

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2690.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2690
    
----
commit a4dbe0c8db4bd8fee1a508ae212f80fa7c8bb824
Author: Ufuk Celebi <uce@apache.org>
Date:   2016-10-24T16:01:28Z

    [FLINK-4894] [network] Don't request buffer after writing to partition
    
    After emitting a record via the RecordWriter, we eagerly requested
    a new buffer for the next emit on that channel (although it's not clear
    that we will immediately need it). With this change, we request that
    buffer lazily when an emit call requires it.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---