Drivers discovered in testing for PM-1452 that a cursor created by a retryable bulkWrite will not be able to be getMore'd. This is because the cursor grabs the txnNumber off of the opCtx when it is created, assuming that the getMore always comes from a transaction since before bulkWrite this was the case.
When a cursor is created like this you cannot run getMore without a txnNumber, and if you run it with one it will fail due to not being a retryable command, so the cursor information is lost.
Since cursors can now be created from a retryable write we need to fix this behavior.
- related to
-
SERVER-89464 BulkWrite sends getMore to mongod with a txnNumber attached
- Closed
-
SERVER-92335 Fix issue with MigrationDestinationManager failing on rangedeletionutil::checkForConflictingDeletions() when it results in running the getMore command
- Closed