Operational Defect Database
BugZero found this defect 222 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2470898
Make $merge inside a $lookup behave the same in replicaset and sharded cluster when db does not exists
Last update date:
3/13/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 aggreagation with a $merge inside a $lookup, the server will return a 51047 error code no matter if the database exists or not. On the other hand, if the same query is processed by a router in a sharded cluster, the router will reply with a 51047 error code if the database already exists and instead will return status OK if the database doesn't exist. To stress this code path, you can use this pre-existing test case and very how the behavior change if you drop the database before running the aggregation.
Top User Comments
mickey.winters commented on Fri, 10 Nov 2023 16:40:52 +0000: pausing because of overlapping work in SERVER-75856 JIRAUSER1270902 commented on Wed, 11 Oct 2023 17:08:42 +0000: tommaso.tocci@mongodb.com I think you are correct. This looks like a corner case that should have been covered under SERVER-69836 but sadly was not. Thank you for reporting it. tommaso.tocci commented on Tue, 10 Oct 2023 17:26:26 +0000: CC colin.stolley@mongodb.com is this related to SERVER-69836 ?
Steps to Reproduce
