[SERVER-57749] Query marked as SBE compatible, but later optimization sends it down an unimplemented path Created: 16/Jun/21 Updated: 29/Oct/23 Resolved: 17/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Arun Banala | Assignee: | Andrii Dobroshynski (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sbe-post-v1, sbe-rollout | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Query Execution 2021-07-12, Query Execution 2021-07-26, QE 2021-08-09, QE 2021-08-23 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 120 | ||||||||||||||||
| Description |
|
We could fix it by implementing ExpressionCoerceToBool in SBE. But it would also be important to double-check that we select SBE only at a point that we know everything will be SBE compatible (i.e. after all optimizations are complete). |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 17/Aug/21 ] |
|
Author: {'name': 'Andrii Dobroshynski', 'email': 'andrii.dobroshynski@mongodb.com', 'username': 'dobroshynski'}Message: |
| Comment by Kyle Suarez [ 22/Jun/21 ] |
|
As part of this ticket, we want to also investigate deferring the decision on whether to use SBE or not to a later point, after all optimizations have been completed. |