RussellSpitzer commented on issue #17206: URL: https://github.com/apache/iceberg/issues/17206#issuecomment-4982150028
I'm strongly opposed to changing this behavior. When we reach a condition which is in express violation of the spec, I don't think we should attempt to "fix" it on read. While we want to be generous in what input we handle, the moment that input violates known invariants I think we should break hard. In the case that a table is broken, a user should be reverting back to a pre-corrupt state. Or manually repairing the table via some other means. I do not think we can just make assumptions about the state of the table (all dv's are valid and can be merged) and just successfully read. -- 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]
