[SERVER-83994] Figure out how "trySbeRestricted" interacts with persistent query settings Created: 07/Dec/23 Updated: 31/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: | |
| Story Points: | 1 |
| Description |
|
When the persistent query setting to use "sbe" for a query is enabled and the framework control knob is set to "trySbeRestricted", what should happen? Should this cause the query to use SBE if it is eligible in "trySbeRestricted" mode or should it cause the query to use SBE if it is eligible in "trySbeEngine" mode? |