[SERVER-82462] Make $densify behave the same in replicaset and sharded cluster when db does not exists Created: 26/Oct/23 Updated: 05/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pm3278-m1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
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. |