Full data integrity check draft #75
Open
+239
−51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The main idea: We scan over all the documents, hashing them, multiplying hashes (order-independent check, xor can be used as an alternative) and then using the same logic as in basic verification to combine the resulting hashes with the respecting namespaces and get the final hash.
The cons of this approach -- it takes the same amount of time as the reading of the whole DB. There are different ways that we could use to improve the performance (e.g. hashing on the server side using js functions), but this approach is not universal and should be tested across different DBMS separately. Probably, an optimization, that can be implemented in the future.
The code is a draft, which means:
--verify-fully
).