-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Sharding EMEA
-
Minor Change
-
Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17, Sharding EMEA 2023-05-15
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
- is caused by
-
SERVER-60926 Make enableSharding command optional
- Closed
- is depended on by
-
COMPASS-6757 Investigate changes in SERVER-63983: Remove deprecated enableSharding flag
- Closed
- is related to
-
MONGOSH-1438 Remove expectation that `partitioned` field is present in config.databases
- Closed