[SERVER-77178] Handle sharded time-series updateOne / updateMulti that changes the shard key field value Created: 16/May/23  Updated: 29/Oct/23  Resolved: 01/Jun/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Yuhong Zhang Assignee: Yoon Soo Kim
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-76453 Support sharded time-series multi upd... Closed
is depended on by SERVER-77607 Support updateOne on a sharded timese... Closed
is depended on by SERVER-76871 Support findAndModify update on a sha... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Sprint: QI 2023-06-12
Participants:

 Description   

When an updateOne changes the shard key field value the updated document (measurement in our case) needs to be moved to the right shard. We have similar handling in the update stage now but instead of performing (delete on the old shard + insert on the new shard), we would want to (update the bucket document on the old shard + insert a bucket document on the new shard) directly on the bucket namespace.



 Comments   
Comment by Githook User [ 01/Jun/23 ]

Author:

{'name': 'Yoonsoo Kim', 'email': 'yoonsoo.kim@mongodb.com', 'username': 'yun-soo'}

Message: SERVER-77178 Handle shard key update on a sharded timeseries collection
Branch: master
https://github.com/mongodb/mongo/commit/0ef2c68f58ea20c2dde99e5ce3ea10b79e18453d

Generated at Thu Feb 08 06:34:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.