Mailing-List: contact dev-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.apache.org
From: sandeshh <git@git.apache.org>
To: dev@apex.incubator.apache.org
Reply-To: dev@apex.incubator.apache.org
References: <git-pr-350-apex-core@git.apache.org>
In-Reply-To: <git-pr-350-apex-core@git.apache.org>
Subject: [GitHub] apex-core pull request #350: APEXCORE-222 Purging the stale data present in ...
Content-Type: text/plain
Message-Id: <20160712002156.437D4DFFF8@git1-us-west.apache.org>
Date: Tue, 12 Jul 2016 00:21:56 +0000 (UTC)
archived-at: Tue, 12 Jul 2016 00:22:00 -0000

GitHub user sandeshh reopened a pull request:

    https://github.com/apache/apex-core/pull/350

    APEXCORE-222 Purging the stale data present in the bufferserver, dire…

    …ctly from the streaming container.

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

    $ git pull https://github.com/sandeshh/apex-core APEXCORE-222

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

    https://github.com/apache/apex-core/pull/350.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 #350
    
----
commit 36e3d333d0c4f22d07701cefacaacae0ab81a0eb
Author: sandeshh <sandesh.hegde@gmail.com>
Date:   2016-06-28T03:58:07Z

    APEXCORE-222 purging of the buffer server is done from the streaming container, instead of StreamingContainerManager

----


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