[DOCS-15191] [Server] Investigate changes in SERVER-64142: Add new enforceUniqueness to refineCollectionShardKey command Created: 28/Mar/22  Updated: 13/Nov/23  Resolved: 19/Apr/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 6.0.0-rc0, 5.0.12, 4.4.17, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Jocelyn Mendez
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-64142 Add new enforceUniqueness to refineCo... Closed
Participants:
Days since reply: 1 year, 23 weeks, 6 days ago
Epic Link: DOCSP-19446

 Description   
Original Downstream Change Summary

Added 2 new fields to the refineShardKey command:
enforceUniquenessCheck: Controls whether this command verifies that any unique indexes are prefixed by the new shard key pattern if unique is true. If true then it will verify and if false then it won't. Defaults to true.

Not strictly required to be in 6.0 docs, but eventually in the docs. These new fields are mostly for use by cluster to cluster replication and documentation is mostly for other mongo engineers. Not sure if there's a better place to put it aside from the docs.

Description of Linked Ticket

(Analogous to SERVER-63732 but for the refineCollectionShardKey command. An implicitlyCreateIndex parameter isn't relevant for refineCollectionShardKey because the command won't attempt to create an index even when the collection is empty.)

enforceUniqueness defaults to true and when set to false, ignores uniqueness property when validating indexes for refineCollectionShardKey.

Regardless of both settings, refineCollectionShardKey should still return an error if there are no index that is compatible with the new shard key pattern.



 Comments   
Comment by Education Bot [ 25/Aug/22 ]

Fix Version updated for upstream SERVER-64142:
6.0.0-rc0, 4.4.17, 5.0.12

Comment by Education Bot [ 24/Aug/22 ]

Fix Version updated for upstream SERVER-64142:
6.0.0-rc0, 5.0.12

Comment by Jess Mokrzecki [ 28/Mar/22 ]

Fix Version updated for upstream SERVER-64142:
6.0.0-rc0

Comment by Jess Mokrzecki [ 28/Mar/22 ]

Fix Version updated for upstream SERVER-64142:
6.0.0, 6.0.0-rc0

Comment by Max Hirschhorn [ 28/Mar/22 ]

Given that we don't want end users to ever use enforceUniquenessCheck:false, I'm not sure we should have the option documented in our public-facing document? We don't have a great story for internal-documentation as far as I know but maybe Server can point other teams to the .idl file for the command as a way?

Comment by Jess Mokrzecki [ 28/Mar/22 ]

Fix Version updated for upstream SERVER-64142:
6.0.0

Generated at Thu Feb 08 08:12:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.