anishshri-db commented on PR #45503: URL: https://github.com/apache/spark/pull/45503#issuecomment-2015886412
@sahnib - yes we did discuss this and @HeartSaVioR - please do correct me if I'm wrong. but basically within the schema, you can say whether a column is nullable or not. However, Spark doesn't disallow writing "null" values for such columns. So this kind of validation would need to happen at the caller, if we want to block writing "null" values for columns defined as non-nullable. However, in some cases the plan could also change the nullability of columns across runs. So instead, we decided to just handle null values and we would keep a single byte mapping per column for each row and simplify this contract a bit -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
