Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17293
Uh.. I am actually not sure if we want the non-nullability per
https://github.com/apache/spark/pull/14124#issuecomment-259615392.
I am willing to help test and verify if it is okay for non-nullability at
my best but I hope anyone who is qualified decides what we want first.
Another personal humble opinion is, I think we should enable/disable this
for all datasource or not (assuming this PR enables non-nullability for Parquet
only).
cc @cloud-fan, @marmbrus and @liancheng, do we want to enable this
non-nullability?
---
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]
