[SERVER-75111] Query sampling should store the "let" field for each read query Created: 21/Mar/23 Updated: 29/Oct/23 Resolved: 30/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding NYC 2023-04-03 | ||||
| Participants: | |||||
| Linked BF Score: | 43 | ||||
| Description |
|
Currently, only the filter and collation are stored. So for a find and aggregate query whose filter refers to variables defined in "let" or "runtimeConstants" (e.g. here), the analyzeShardKey command wouldn't be able to evaluate the filter and do the synthetic routing. This would cause the command to fail with a PlanExecutor error just as shown in BF-28087. |
| Comments |
| Comment by Githook User [ 30/Mar/23 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |