-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2022-02-21, Execution Team 2022-03-07
Say coll1 (with uuid1) is sharded and coll2 (with uuid2) is unsharded, and the command {insert: coll1, documents: [{_id: 1}], collectionUUID: uuid2} is issued where the document {_id: 1} belongs on the non-primary shard. Then the returned CollectionUUIDMismatch will erroneously not contain coll2, because it only exists on the primary shard. We should make sure that regardless of which shards are targeted and no matter whether collections are sharded are unsharded, the CollectionUUIDMismatch contains all of the information that it should.
- causes
-
SERVER-79049 Server returns unexpected CollectionUUIDMismatch with actual collection name equal to expected collection name
- Closed
- is related to
-
SERVER-64872 Aggregate with collectionUUID on sharded cluster can incorrectly omit the actual collection
- Closed