[SERVER-46474] Require ExpressionContext before creation of CanonicalQuery Created: 28/Feb/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | storch | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
Currently it is possible to pass a null expression context to CanonicalQuery::canonicalize(). If this happens, CanonicalQuery will create one for you. This behavior is confusing and bug-prone. Instead, operations should create an ExpressionContext up front and thread it through the places which need it. |