Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
Fully Compatible
-
ALL
-
v4.2
-
Query 2019-08-12, Query 2019-08-26, Query 2019-09-09
-
0
Description
Perhaps the aggregation code should handle 0 shards?
Or should sharding prevent dropping config.shards? Sharding has discussed before not wanting to disallow direct writes to the config database, since sometimes people do that, and I think mongorestore might drop some of the config collections.
We could also prevent the fuzzer from dropping config collections to prevent the build failures.