You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by gyfora <gi...@git.apache.org> on 2015/03/17 20:11:12 UTC

[GitHub] flink pull request: [FLINK-1706] Spilling BarrierBuffer added + ba...

GitHub user gyfora opened a pull request:

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

    [FLINK-1706] Spilling BarrierBuffer added + basic tests

    This commit introduces disk spilling for the BarrierBuffers based on the availability of the buffers in the buffer pools of the input gates.
    
    This is a first version, with proper resource cleanup still missing.
    
    I am putting it up here for review as this is a critical part of the ft logic.

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

    $ git pull https://github.com/mbalassi/flink FLINK-1706

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

    https://github.com/apache/flink/pull/493.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 #493
    
----
commit 7b0cc330a9717110f53fe24535a59b830f420eb3
Author: Gyula Fora <gy...@apache.org>
Date:   2015-03-17T16:39:27Z

    [FLINK-1706] Spilling BarrierBuffer added + basic tests

----


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

[GitHub] flink pull request: [FLINK-1706] Spilling BarrierBuffer added + ba...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


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