[SERVER-81560] Collection writes using batch writer should work more like regular writes Created: 29/Sep/23 Updated: 29/Oct/23 Resolved: 10/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Henrik Edin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution NAMR Team 2023-10-16 |
| Participants: |
| Description |
|
When using the BatchedCollectionCatalogWriter in combination with WriteUnitOfWork the cloned writable collection instance should roll back and be discarded like it behaves for regular writes when the WUOW rolls back. Currently, stale state can leak into the writable collection instance when the WriteUnitOfWork rolls back, making it more difficult to rely on the copy-on-write semantics over having to manually implement onRollback handlers. |
| Comments |
| Comment by Githook User [ 10/Oct/23 ] |
|
Author: {'name': 'henrikedin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: Code that is shared with batched write can then rely on the writable Collection instance to be discarded in the case of rollback. |