[SERVER-64069] Relax restriction that changing a document's shard key value must have a transaction number Created: 01/Mar/22 Updated: 29/Oct/23 Resolved: 02/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | [DO NOT USE] Backlog - Sharding NYC |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding NYC
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 2022-07-11, Sharding 2022-07-25, Sharding 2022-08-08 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 151 | ||||||||||||
| Description |
|
Updates/findAndModifies that change a document's shard key value require the user ran the operation in a retryable write or transaction so there's either an active transaction or a transaction number to use for a spawned internal transaction that atomically deletes and inserts the document. We can now use the transaction API to remove this restriction, since writes without a transaction number will create an internal session for the transaction so there's no need to reuse a client provided transaction number. |
| Comments |
| Comment by Githook User [ 02/Aug/22 ] |
|
Author: {'name': 'Erin Liang', 'email': 'erin.liang@mongodb.com', 'username': 'erl-ang'}Message: |
| Comment by Githook User [ 28/Jul/22 ] |
|
Author: {'name': 'Sviatlana Zuiko', 'email': 'sviatlana.zuiko@mongodb.com', 'username': 'szuiko'}Message: Revert " This reverts commit 5c57650600140a15cc1e9e91fe362f42b99a9920. |