Operational Defect Database
BugZero found this defect 206 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2483631
Make $densify behave the same in replicaset and sharded cluster when db does not exists
Last update date:
3/14/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
On replicaset if we send an aggregation with a $densify stage with a namespace for which the database haven't been created yet and the $densify stage would produce more docs than the configured internalQueryMaxAllowedDensifyDocs parameter the aggregation will fail with 5897900 error code. On the other hand, if the same aggregation is executed on a sharded cluster the aggregation will simply work with no error.
Top User Comments
mickey.winters commented on Thu, 14 Mar 2024 15:05:40 +0000: both this ticket and https://jira.mongodb.org/browse/SERVER-82096 have this same issue where we can't generate right error due to the collection not existing and we can't run the query against a mongod so we return an empty response. perhaps this is acceptable, maybe we want to return namespace not found in these cases, or maybe we should add some functionality to mongos to run the pipeline/query against $documents.
Steps to Reproduce
