[SERVER-82479] Clarify multitenancy passthrough failure in lookup_query_stats.js Created: 26/Oct/23 Updated: 09/Nov/23 Resolved: 09/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.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 |
|
Both multitenancy_with_mongoq_jscore_passthrough and multitenancy_with_atlas_proxy_jscore_passthrough will fail running the lookup_query_stats.js test when asserting scannedObjects counts obtained using the serverStats command. This occurs after creating indexes for foreign fields in |
| Comments |
| Comment by Githook User [ 07/Nov/23 ] |
|
Author: {'name': 'Hugh Tong', 'email': 'hugh.tong@mongodb.com', 'username': 'cortrain'}Message: |