[SERVER-45256] Complete TODO listed in SERVER-44138 Created: 19/Dec/19  Updated: 07/Jan/20  Resolved: 07/Jan/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: PM Bot Assignee: Maria van Keulen
Resolution: Done Votes: 0
Labels: autogen-todo
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-44138 Stash UncommittedCollections resource... Closed
Sprint: Execution Team 2020-01-13
Participants:

 Description   

There is a TODO in the codebase referencing a resolved ticket which is assigned to you.

Please follow this link to see the lines of code referencing this resolved ticket:
https://github.com/mongodb/mongo/search?q=SERVER-44138&type=Code

The next steps for this ticket are to either remove the outdated TODO or follow the steps in the TODO if it is correct. If the latter, please update the summary and description of this ticket to represent the work you're actually doing.



 Comments   
Comment by Maria van Keulen [ 07/Jan/20 ]

This TODO has been addressed as of SERVER-44139.

Comment by Maria van Keulen [ 20/Dec/19 ]

After a second look, the comment referenced in this ticket assumed that SERVER-44138 would result in the ability to perform multiple collection creations in the same WriteUnitOfWork. However, in SERVER-44138 we rely on the TransactionParticipant framework to ensure availability of UncommittedCollections from OperationContext to OperationContext, rather than moving the UncommittedCollections logic into the RecoveryUnit. The test cases referenced in this comment are therefore still not possible.

Comment by Maria van Keulen [ 19/Dec/19 ]

This TODO is not possible as of SERVER-44138, but should be possible as of SERVER-44139.

Generated at Thu Feb 08 05:08:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.