| commit | 90c4a9489045805f1ffe87bada2ba09bf00a2aa5 | |
| author | Arunachalam Thirupathi <arunachalam.t@gmail.com> | |
| Wed, 21 May 2014 18:40:19 +0000 (21 11:40 -0700) | ||
| committer | Arunachalam Thirupathi <arunachalam.t@gmail.com> | |
| Wed, 21 May 2014 18:40:19 +0000 (21 11:40 -0700) | ||
| tree | a19e1edcce0f99fad839570faae38abb4622dde1 | treesnapshot (tar.gz zip) |
| parent | 62a5878747b54d3b978ad373a32004c49176888a | commitdiff |
Add overwrite option to fork lift tool
If the key already exists in the destination cluster, forklift tool
will not overwrite the key. With the intent of supporting read only
cluster data to be fork lifted to the read/write cluster, overwrite
option is being added. If the newly forklifted data does not contain
the entire key set from the old, then the new data will be the mix
of old and new. The old data should expire sooner than the new one
enforced by the retention policy.
If the key already exists in the destination cluster, forklift tool
will not overwrite the key. With the intent of supporting read only
cluster data to be fork lifted to the read/write cluster, overwrite
option is being added. If the newly forklifted data does not contain
the entire key set from the old, then the new data will be the mix
of old and new. The old data should expire sooner than the new one
enforced by the retention policy.