You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2020/03/15 18:06:26 UTC
[GitHub] [spark] srowen commented on issue #27918:
[SPARK-31071][SQL][Follow-up] Support nonnull annotation by field directly
srowen commented on issue #27918: [SPARK-31071][SQL][Follow-up] Support nonnull annotation by field directly
URL: https://github.com/apache/spark/pull/27918#issuecomment-599244277
I'm saying it's possible that the property is nullable but some underlying field is not, in which case, you don't want to consider it non-nullable right? but wondering if this is even a plausible use case, even if it's possible in code.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org