cloud-fan commented on PR #25536: URL: https://github.com/apache/spark/pull/25536#issuecomment-1410668683
This is a good point. If Spark can do schema evolution during table insertion, then having non-nullable table schema in CTAS is not a problem anymore. We need a bit design about how data sources can claim its support of schema evolution, and what if they do want to enforce the non-nullable property. -- 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]
