ValidateState does extra filtering regarding what indexes to validate, making sure indexes are ready and in the checkpoint, whereas IndexConsistency does not. Additionally, IndexConsistency currently opens its own cursor and so could be looking at indexes in a different checkpoint than the one used by ValidateState, creating an inconsistent view.
IndexConsistency constructor should use ValidateState's index list rather than simply durable indexes
- Votes:
-
0 Vote for this issue
- Watchers:
-
1 Start watching this issue
- Created:
- Updated:
- Resolved: