[SERVER-39780] Throw WouldChangeOwningShard exception if write will cause document to change shards Created: 22/Feb/19 Updated: 29/Oct/23 Resolved: 07/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2019-02-25, Sharding 2019-03-11 | ||||||||
| Participants: | |||||||||
| Description |
|
Before applying the post-image, the update node should check whether this node owns the chunk that the shard key in the post-image belongs to. If it does not own this chunk, it should throw WouldChangeOwningShard. If the write is in a multi-statement transaction, it should attach the original query predicate and post-image. If it is not, it should attach the original query predicate and update fields. |
| Comments |
| Comment by Githook User [ 07/Mar/19 ] |
|
Author: {'name': 'jannaerin', 'username': 'jannaerin', 'email': 'golden.janna@gmail.com'}Message: |