-
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
We need to understand the cost of the type inference used for arrayness checks.
There's at least two cases:
- the public canPathBeArray API being queried which can run inference
- when building the graph, such as for renames where the base field has unknown arrayness.
- is related to
-
SERVER-136153 Unify canPathBeArray handling in the graph to use type information
-
- In Progress
-