[SERVER-60120] (Sharded) support updates to fields in a document's cluster key Created: 21/Sep/21  Updated: 05/Dec/22  Resolved: 05/Dec/22

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

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: PM-2311-M3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Storage Execution
Participants:

 Description   

This ticket should incorporate

(1) updates to fields in a documents cluster key when the collection is not sharded with any of said fields (see if SERVER-60119 already enables this)

(2) updates to fields in a documents cluster key when the fields are included in the shard key  — for context, this may already work as it does with non-clustered collections.

How sharded collections handle shard key updates today (non-clustered):
The mongos sends an update, if the update modifies a document's shard key, an error gets propagated back to the mongos, and the mongos issues a delete for the preimage and insert for the postimage in a multi-document transaction. Clustered collections should behave the same as non-clustered collections in this way.


Generated at Thu Feb 08 05:49:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.