GitHub user aljoscha opened a pull request:
https://github.com/apache/flink/pull/1879
[FLINK-3718] Add Option For Completely Async Backup in RocksDB State Backend
This also refactors the RocksDB backend to keep one RocksDB data base in
the backend where all key/value state is stored. Individual named
key/value states get a reference to the db and store their state in a
column family. This way, we only have to backup one RocksDB data base
and can centrally decide how to do backups.
@tillrohrmann I don't how much these changes clash with your work on
repartitionable state. Would it make sense to wait with this PR or can it go
ahead before your changes go in?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aljoscha/flink rocks-refactor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1879.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 #1879
----
commit 6b7123a2ff5db0a49896d58d09b0ba541fbb8135
Author: Aljoscha Krettek <[email protected]>
Date: 2016-04-08T12:58:50Z
[FLINK-3718] Add Option For Completely Async Backup in RocksDB State Backend
This also refactors the RocksDB backend to keep one RocksDB data base in
the backend where all key/value state is stored. Individual named
key/value states get a reference to the db and store their state in a
column family. This way, we only have to backup one RocksDB data base
and can centrally decide how to do backups.
----
---
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.
---
