[SERVER-32976] Rename the `isAssignedShardKey` field to `sharded` in config.collections Created: 29/Jan/18  Updated: 27/Oct/23  Resolved: 12/Nov/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.1
Fix Version/s: Needs Further Definition

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Gone away Votes: 0
Labels: max-triage, pm-1051-legacy-tickets
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

The word "sharded" is more brief and descriptive than "isAssignedShardKey".



 Comments   
Comment by Max Hirschhorn [ 12/Nov/21 ]

The isAssignedShardKey field in the config.collections entries was removed in the changes from eb0a38f as part of SERVER-42365.

Comment by Kaloian Manassiev [ 02/Mar/18 ]

renctan, since this technically belongs to Part 2 of the project, should we just get rid of this field for now, since it is not used anywhere?

Generated at Thu Feb 08 04:31:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.