Issue #, if available:
As a DB specific cleanup job, mergeTombstoneFiles is only valuable at db open when isCleanUpTombstonesDuringOpen is true. So instead of exposing it to client, it makes more sense to keep it as internal procedure and do it with a background thread right after in-memory index is built in db open.
Description of changes:
Remove the public API mergeTombstoneFiles
Do tombstone file merge during db open
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
@bellofreedom @amannaly @finaldie
Issue #, if available: As a DB specific cleanup job,
mergeTombstoneFiles
is only valuable at db open whenisCleanUpTombstonesDuringOpen
istrue
. So instead of exposing it to client, it makes more sense to keep it as internal procedure and do it with a background thread right after in-memory index is built in db open.Description of changes:
mergeTombstoneFiles
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.