[SERVER-53063] Make CollectionCatalogStasher support nesting usage Created: 24/Nov/20 Updated: 27/Oct/23 Resolved: 08/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Execution Team 2020-11-30, Execution Team 2020-12-14 |
| Participants: |
| Description |
|
The AutoGetCollectionForReadLockFree has a CollectionCatalogStasher and CollectionCatalogStasher currently will not support multiple instances on an OperationContext. However, the DBDirectClient can take a nested AutoGetCollectionForReadLockFree, along with a CollectionCatalogStasher. Therefore, nesting must be supported. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 08/Dec/20 ] |
|
Don't believe this is necessary anymore. Closing. |