Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18576
Conceptually, nullability of each column is still a hint to Spark SQL. In
the constraint inference, we also add `ISNOTNULL` in
[`constructIsNotNullConstraints`
](https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/QueryPlanConstraints.scala#L55-L70
).
It can simplify the codegen in many cases and also help the optimization
rules e.g., `EliminateOuterJoin`. It might be a good idea to add another trait
for nullability hints, instead of changing the operator interfaces. cc @rxin
@sameeragarwal
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
