-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.6.0
-
Fully Compatible
-
ALL
-
Sharding 2018-02-12, Sharding 2018-02-26
Some of the variants of AutoGetCollectionOrView and AutoGetCollectionOrViewForReadCommand perform shard version checking on a namespace that is a view and not collection. This is wrong at least because it causes double checking (once for the view and once for the underlying collection), however more importantly it makes it impossible to make unsharded collections tracked on the config server.
- causes
-
SERVER-33624 Commands which accept UUIDs do not correctly validate that the collection belongs to the database over which the command was issued
- Closed
- depends on
-
SERVER-29909 Libraries db/db_raii and db/s/sharding are directly cyclic
- Closed
- is depended on by
-
SERVER-32198 Missing collection metadata on the shard implies both UNSHARDED and "metadata not loaded yet"
- Closed
- is related to
-
SERVER-33632 Make UUID catalog reload atomic
- Closed
- related to
-
SERVER-35699 Avoid holding locks during query parsing
- Backlog