[SERVER-82434] Fix $merge implicitly creating incorrect database Created: 25/Oct/23 Updated: 30/Oct/23 Resolved: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Hugh Tong (Inactive) | Assignee: | Hugh Tong (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Service Arch 2023-10-30, Service Arch 2023-11-13 | ||||||||
| Participants: | |||||||||
| Description |
|
multitenancy_with_atlas_proxy_jscore_passthrough is failing $merge operations in aggregation piplines where the database is implicitly being created. The several tests are failing in the same way and are likely related. |
| Comments |
| Comment by Githook User [ 30/Oct/23 ] |
|
Author: {'name': 'Hugh Tong', 'email': 'hugh.tong@mongodb.com', 'username': 'cortrain'}Message: |