In a case, mongodb sees the largest key returns a prepared conflict error (link here). We should not return that error as the largest key should ignore all visibility check.
- causes
-
WT-8241 Skip value return for largest key
- Closed
- is caused by
-
WT-7992 Provide API to return the last key in a table regardless of visibility
- Closed
- is depended on by
-
SERVER-58409 Startup RecordId initialization is flawed with durable history and reconstructing prepared transactions
- Closed