-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-14111][SQL] Correct output nullability with constraints for logical plans #11926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ith-constraint Conflicts: sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/InferFiltersFromConstraintsSuite.scala
…ith-constraint3 Conflicts: sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicOperators.scala
|
Test build #53997 has finished for PR 11926 at commit
|
|
retest this please. |
|
Test build #54002 has finished for PR 11926 at commit
|
|
retest this please. |
|
Test build #54015 has finished for PR 11926 at commit
|
|
retest this please. |
|
Test build #54024 has finished for PR 11926 at commit
|
|
retest this please. |
|
Test build #54045 has finished for PR 11926 at commit
|
|
Test build #54164 has finished for PR 11926 at commit
|
|
Test build #54283 has finished for PR 11926 at commit
|
|
The failed tests are due to another bug in |
|
Close this and think better solution. |
What changes were proposed in this pull request?
JIRA: https://issues.apache.org/jira/browse/SPARK-14111
We use output of logical plan as schema. Output nullablity is important and we should keep its correctness.
With constraints and optimization, in fact we will change output nullability of logical plans. But we don't reflect such changes in the output attributes. So the output nullablity is not correct now.
How was this patch tested?
Modified
InferFiltersFromConstraintsSuiteandAnalysisSuite. Existing tests.