Github user sameeragarwal commented on the pull request:
https://github.com/apache/spark/pull/11649#issuecomment-195238973
@gatorsmile this change makes sense to me, however what are your thoughts
on slightly widening the scope of this change and not generating `IsNotNull`
constraints for any compound expression (in `constructIsNotNullConstraints`)?
As you pointed out, I can't think of an optimization that can make use of these
non-nullability constraints for compound expressions. Later, we can always
extend `constructIsNotNullConstraints` to infer `isNotNull` constraints for
individual attributes from compound expressions.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
