Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
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 duplicated by

SERVER-115361 Ensure we do not assert if invalid "FieldPath" is passed into isPathArray()

Closed

is related to

SERVER-113446 Investigate using FieldRef instead of FieldPath

Closed

related to

SERVER-116314 Refactor FieldPath constructor to use factory function

Closed

SERVER-117655 Avoid assigning FieldPath object to *this in constructor

Backlog

SERVER-115361 Ensure we do not assert if invalid "FieldPath" is passed into isPathArray()

Closed

Assignee:: Natalie Hill
Reporter:: Naafiyan Ahmed
Participants:: Githook User, Naafiyan Ahmed, Natalie Hill
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Nov 03 2025 10:02:10 PM UTC
Updated:: Jan 22 2026 06:42:54 PM UTC
Resolved:: Jan 12 2026 01:34:10 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates