[SERVER-64872] Aggregate with collectionUUID on sharded cluster can incorrectly omit the actual collection Created: 24/Mar/22  Updated: 29/Oct/23  Resolved: 31/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-64875 Support specifying collectionUUID in ... Closed
Related
related to SERVER-62563 Support sharding for collectionUUID p... Closed
related to SERVER-63285 Ensure CollectionUUIDMismatch error f... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2022-04-04
Participants:

 Description   

For example if the primary shard does not own any chunks for the collection being queried, $indexStats will not target that shard. Then if the actual collection is unsharded, the actualCollection field of the CollectionUUIDMismatch will not be populated even though it should be. More generally, this can occur if there are no shards that contain chunks for both collections. This should be able to be solved with the same approach as SERVER-63285.



 Comments   
Comment by Githook User [ 31/Mar/22 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-64872 Ensure `CollectionUUIDMismatch` from sharded `aggregate` does not incorrectly omit the actual collection
Branch: master
https://github.com/mongodb/mongo/commit/2d78530f2b590d205232bd3d65cb8f66500aa86f

Generated at Thu Feb 08 06:01:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.