forked from basho/yokozuna
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
Don't run extraction on tombstones
Riak KV has a 2-phase delete. 1. Write a tombstone value. 2. Reap the tombstones and delete data at backend level. Yokozuna must honor both phases because the tombstone value could live for an unspecified amount of time due to either configuration or failure. Since active anti-entropy and other sub-systems may consider a tombstone an object Yokozuna must know about it even if there is no content to index. Since the tombstone object is void of content no extraction needs to be performed. Only the special _yz fields need to be written.
- Loading branch information
Showing
4 changed files
with
37 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters