This hash will be calculated by performing a natural order scan of the collection and calculating an MD5 hash of the document. The resulting MD5 hash will be combined into a 'total' hash by performing XOR against the existing 'total' hash, resulting in an order independent hash that should be consistent across nodes
This ticket should include a basic jstest that covers the following scenarios
- Nodes with exact matching documents (same order) give the same output
- Nodes with different number of documents give different output
- Nodes that have one document with different content give different output
- Nodes that have the same document inserted in different orders give the same output
Output needs to be added to ValidateResults object and the implementation of appendToResultObj
This code needs to be added around here where we traverse the record store. Example code for using md5 hashing is here from dbhash
- depends on
-
SERVER-109939 Add new inputs to extended validate command
-
- Closed
-
- is depended on by
-
-
- Backlog
-
-
-
- Backlog
-
-
-
- Closed
-
- related to
-
-
- In Progress
-
-
-
- Closed
-