GitHub user ashishtadose opened a pull request:
https://github.com/apache/incubator-apex-core/pull/184
APEXCORE-283 - checkpointing in distributed in-memory store
@tushargosavi
Can you please review the changes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashishtadose/incubator-apex-core
APEXCORE-283.checkpoint
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-core/pull/184.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 #184
----
commit 1988d460e921dc82249d60c0bbe5a1f1b5913910
Author: Ashish <[email protected]>
Date: 2015-12-09T14:45:27Z
APEXCORE-283 #comment Interface for storage agent to retrieve application id
commit f23c6814bf2964dc46d50f60ad93e4faa94b3880
Author: Ashish <[email protected]>
Date: 2015-12-09T14:48:44Z
APEXCORE-283 #comment Abstract implementation of KeyValue storage agent
which can be configured with implementation of KeyValue store for checkpointing.
commit f092f046810acfaeb00955ffcde6a3e6c27cff4d
Author: Ashish <[email protected]>
Date: 2015-12-09T14:53:02Z
APEXCORE-283 #comment Concrete implementation of In memory storage agent
for Apache Geode
commit ab110cb0e77bfd50991fd16abc01fada7201e781
Author: Ashish <[email protected]>
Date: 2015-12-09T15:11:00Z
APEXCORE-283 #comment Updated AppIdAwareStorage agent changes in
StramLocalCluster
commit aae555660022051a367f7be822833098f8dcc8fb
Author: Ashish <[email protected]>
Date: 2015-12-09T15:14:10Z
APEXCORE-283 #comment Excluded Geode storage related test cases as it
requires some manual setup
commit 142f0212eccda92dca90569f79d9c8a5a9874439
Author: Ashish <[email protected]>
Date: 2015-12-09T15:15:42Z
APEXCORE-283 #comment fixed checkstyle fixes causing build failures
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
