-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Query Execution 2021-02-22, Query Execution 2021-03-08, Query Execution 2021-03-22, Query Execution 2021-04-05, Query Execution 2021-04-19, Query Execution 2021-05-03
In a CR for SERVER-51666 it was pointed out that there could be some inconsistencies between how expression argument checks are done in the classic in SBE engines. For example, in the classic engine some expressions may follow all-checks-per-argument rule (by applying all checks on one arguments before moving to the next one), whilst in SBE the same expression may follow one-check-for-all-arguments rule (when we apply a specific check for all arguments before moving to the next type of check, for example check all arguments for null, and then validate the range). We should keep this behaviour consistent between the two engines and will need to investigate and find all expressions in SBE which check arguments differently than their counterparts in the classic engine and address such inconsistencies.
- is depended on by
-
-
- Closed
-
- is duplicated by
-
SERVER-56084 [SBE] aggregation_multiversion_fuzzer fails with SBE on due to different results from $graphLookup
-
- Closed
-
- related to
-
-
- Closed
-
-
SERVER-56278 Make $replaceOne check for any null arguments first
-
- Backlog
-