Github user marmbrus commented on the issue:

    https://github.com/apache/spark/pull/12337
  
    +1 to this feature!  I think this might be the first step in a better story 
for people trying to use `nullable = false` as an enforcement mechanism (I'd 
bring this idea up on 
[SPARK-17939](https://issues.apache.org/jira/browse/SPARK-17939)).  A few 
thoughts on what we would need to do to commit this:
     - some tests (and make sure the error messages when you hit nulls make 
sense to a user)
     - as a bonus we could check how this affects the constraints on 
nullability (i.e. does the optimzer know that we can skip future null checks)


---
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

Reply via email to