cloud-fan commented on PR #37011: URL: https://github.com/apache/spark/pull/37011#issuecomment-1174087671
> afait if the new schema has field nullable, while the incoming DF is not-nullable, the resulting DF will still have not-nullable field I think stricter nullability is always better? Also I don't find an existing expression to turn a non-nullable input to nullable. > it doesn't propagate metadata/description from the new-schema Supported now > it's fairly hard to invoke this in pyspark Usually, we add python API in a separated PR. Right? @HyukjinKwon -- 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]
