[SERVER-45231] Provide a way to cause a well-defined order of evaluation for predicates Created: 18/Dec/19  Updated: 06/Dec/22  Resolved: 19/Dec/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Jacob Evans Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 0
Labels: qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-37530 Provide a way to cause a well-defined... Backlog
Related
is related to SERVER-37530 Provide a way to cause a well-defined... Backlog
is related to SERVER-45123 Queries should not fail with type err... Closed
is related to DOCS-13309 MongoDB does not guarantee short circ... Closed
Assigned Teams:
Query
Participants:

 Description   

Currently we freely reorder predicates for rewrite and optimization for the sake of performance. We could provide a way to define the order certain predicates are run in so any side effects from them (such as errors being produced) are predictable.



 Comments   
Comment by Jacob Evans [ 19/Dec/19 ]

Alright, all done.

Comment by David Storch [ 19/Dec/19 ]

jacob.evans, this looks closely related to SERVER-37530, which is framed as a bug where this ticket is framed as an improvement. I'd argue that we shouldn't have both tickets open on the backlog, since they describe essentially the same problem. Perhaps we should close this ticket, but reframe SERVER-37530 as an improvement request for users to express a fixed expression evaluation order in their queries?

Generated at Thu Feb 08 05:08:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.