-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently, the PathArrayness API uses FieldPath and the constructor of FieldPath will uassert if we give it an invalid FieldPath even if the actual path is valid in MQL, e.g. empty path in MatchExpressions.
We should validate the input FieldPath by calling FieldPath::validateFieldName() and if we return an error, we should just return the conservative guarantee, i.e. input field path is an array.
- is related to
-
SERVER-113446 Investigate using FieldRef instead of FieldPath
-
- Backlog
-