rdblue commented on pull request #2496: URL: https://github.com/apache/iceberg/pull/2496#issuecomment-1036702844
I doubt that it is worth the complexity of an algorithm like finding the default that should be applied for a file. We _could_ do that by keeping track of when defaults are added with sequence numbers. But I think another reasonable way to fix that problem is just to state that once a default is set, it is an incompatible change to update it to another value. By making it an incompatible change, we could allow modifying the value but make it clear that it is the user's responsibility. We do this when adding a required field to a table. You can add a field by calling `allowIncompatibleChanges()` in the schema update API. But if any files don't have the field and reads fail, that's the user's fault. -- 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]
