-
Type: Bug
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: 2.6.0, 2.6.3
-
Component/s: Index Maintenance, Querying
-
Query Optimization
-
ALL
-
When distinct is called on a field for which there exists a document with an empty array in said field, it will return null in the result if there is an index on the field.
- is depended on by
-
SERVER-53626 Minimize index scanning when retrieving distinct values grouped by more than one field
- Backlog
- is duplicated by
-
SERVER-31343 Distinct over empty indexed arrays produces undefined value in the result
- Closed
-
SERVER-31838 Query planner generates DISTINCT_SCAN without FETCH plan for distinct on dotted field
- Closed
-
SERVER-85229 The same distinct command, the result sometimes contains null and sometimes does not
- Closed
-
SERVER-17457 Inclusion of "null" in "distinct" result depends on existence of index
- Closed
- is related to
-
SERVER-93059 Remove projection for multiplanning in case of distinct command
- Closed
- related to
-
SERVER-85298 distinct command with a winning plan of DISTINCT_SCAN returns null values, whereas COLLSCAN does not
- Closed
-
SERVER-12869 Index null values and missing values differently
- Backlog