[SERVER-61449] Support implicit clustered collection creation via shardCollection() Created: 12/Nov/21  Updated: 07/Jan/22  Resolved: 07/Jan/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: Haley Connelly
Resolution: Won't Do Votes: 0
Labels: PM-2311-M2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-62439 Complete TODO listed in SERVER-61449 Closed
Sprint: Execution Team 2021-11-29, Execution Team 2021-12-13, Execution Team 2021-12-27, Execution Team 2022-01-10, Execution Team 2022-01-24
Participants:

 Description   

We want to be able to create a clustered collection through shardCollection.

One proposal is to accept clustered:true as a parameter.

Once implicit clustered collection is created, we could potentially start running CRUD_clustered_collection.js, along with other tests for clustered collections with sharding currently disabled.

(to enable sharded FSM workloads, we could consider extending $config.$data to include shardCollectionOpts like it does shardKey)



 Comments   
Comment by Haley Connelly [ 07/Jan/22 ]

For now, we determined shardCollection implicit clustered collection creation isn't useful if the cluster key is forced to be the same as the shard key. 

In the future, we could make changes to allow shardCollection to take in the clusteredIndex options we pass into createCollection {clusteredIndex: {key:

{<cluster key pattern>}

, unique: true, ...}}

 

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