-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
We should look into whether we can do something better than validating distinct eligibility twice (see SERVER-93694), e.g. falling back to classic only in cases where distinct multiplanning actually generates a DISTINCT_SCAN, and otherwise using SBE if we can.
- related to
-
SERVER-93694 Address SBE incompatibility for distinct-like queries in distinct multiplanning
- Open