[DOCS-16057] Investigate changes in SERVER-63983: Remove deprecated enableSharding flag Created: 21/Apr/23  Updated: 13/Nov/23  Resolved: 25/Jul/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 7.1.0-rc0
Fix Version/s: 7.1.0-rc0, 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: David Hou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-63983 Remove deprecated enableSharding flag Closed
Participants:
Days since reply: 41 weeks, 5 days ago
Story Points: 2

 Description   
Original Downstream Change Summary

Starting from 7.1 entries in config.databases for newly created databases will not contain anymore the partitioned flag.

Description of Linked Ticket

Starting from 6.0 there is no need anymore to call the enableSharding command on a database before to shard a collection.

In 6.0 we made the partitioned flag in config.databases to be false by default for all newly created database and if this field is not found while parsing from disk it will be considered false.

In version 7.1 we can completely remove this field from the IDL and stop persisting it.

So recapping:

  • binaries ≤ 5.0 ⇒ the field is always persisted either false/true and if not present will be considered false
  • 6.0 ≤ binaries ≤ 7.0 ⇒ the field is always persisted as false and if not present will be considered false
  • binaries >= 7.0 ⇒ the field is neither persisted nor parsed

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