[SPARK-18130][SQL] Don't add inferred redundant isnotnull condition from constraints #15653
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.
What changes were proposed in this pull request?
In
Optimizer, we will infer additional conditions fromFilter's constraints which includeIsNotNull. Some inferredIsNotNulls are useful because they can be short circuit for other predicates which refer the same attributes. But for anIsNotNullcondition, we also infer otherIsNotNullfrom it. ThoseIsNotNulls are redundant. We don't need to include them.E.g., for a condition like
IsNotNull(a + Rand()), an additionalIsNotNull(a)will be added intoFilter's condition. So we need to evaluateIsNotNull(a + Rand()) && IsNotNull(a). Actually we don't needIsNotNull(a)because it is guaranteed by the originalIsNotNull(a + Rand()).How was this patch tested?
Jenkins tests.
Please review https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark before opening a pull request.