Fix incorrect predicate precedence involving OR and split predicates #12078
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If constraintExpressions contain translated
OR
expression and there is a split predicate, resulting predicate could be incorrect:predicate1 OR predicate2 AND splitPredicate
. Instead we need to wrap both sides of OR expression with parens:(predicate1 OR predicate2) AND splitPredicate