[SERVER-57121] Collection isolation should work in SideTransaction Created: 21/May/21 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
The Collection isolation implemented for lock free reads that resides inside the CollectionCatalog is implemented as a decoration on the OperationContext. This leads to SideTransaction's to observe uncommitted state from their parent. Multikey is set inside a SideTransaction and need to operate directly on the DurableCatalog because it cannot trust the metadata in the Collection because of this. The isolation should be implemented either like UncommittedCollections where the TransactionParticipant can detach/attach the state. Or as a decoration on the RecoveryUnit. |