rdblue commented on issue #540: URL: https://github.com/apache/incubator-iceberg/issues/540#issuecomment-631586214
@geota, in Spark, "automatic schema evolution" usually means not validating the schema on write and merging schemas together on read to find what the table schema actually is. This is how the v1 DataFrame APIs work. Calling it "automatic" makes it sound more like a feature and less like a bug. That said, I think it's fine to add this to Iceberg as a real feature -- where we detect the changes and apply them to the table schema. It just shouldn't be the default behavior because it can easily cause problems. Most of the use cases are covered by replace-table-as-select anyway. ---------------------------------------------------------------- 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: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
