Necessary in order to allow concurrent DDL operations.
Drop collection and drop index ops should cause the validate cmd to abort with an error.
Create index should not cause failure, so may require special handling in index iteration somehow? (haven't thought it out).
Index creation and validate should run concurrently without interrupting the validate work. (have not thought this out, but we might need filtering on the index iteration, maybe by timestamp?? – e.g. save a start timestamp, use it to filter the indexes)
- depends on
-
SERVER-30357 Allow users to run the validate cmd with {background:true}
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-41811 Deduplicate CollectionValidation::_genericRecordStoreValidate and ValidateAdaptor::traverseRecordStore
-
- Closed
-
-
-
- Closed
-
- is depended on by
-
-
- Closed
-