[SERVER-85215] Ensure queryFramework hint is applicable to distinct command via query settings Created: 15/Jan/24 Updated: 16/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Denis Grebennicov | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Integration
|
||||||||
| Participants: | |||||||||
| Description |
|
PM-412 added support for query settings for find, agg and distinct commands. However, at the moment of development distinct could only support Classic execution engine. As part of PM-3163, distinct command will be executable via SBE. Since distinct command accepts queryFramework query settings, we need to be sure that if query settings have queryFramework specified, Classic or SBE engines will be picked appropriately. |