We currently open WiredTiger transactions in a lazy manner. As batchSize:0 reads do not need to access collection data, we do not start a WiredTiger transaction until the subsequent getMore.
For readConcern level snapshot reads this is counter-intuitive and allows for reading of writes that occur in-between the find and getMore.
- depends on
-
SERVER-33722 readConcern snapshot should return an error for metadata changes
- Closed
- is duplicated by
-
SERVER-32686 Test snapshot isolation for {batchSize: 0} cursors
- Closed