dannycjones commented on issue #3250: URL: https://github.com/apache/iceberg-rust/issues/3250#issuecomment-5778400873
FYI @blackmwk @CTTY. I plan to have a lot of the validation evaluated late for default values rather than at construction. In other words, we can load the table with a bad default just fine but only on read or write might it fail. The reason for this being that tables with bad defaults may otherwise be working for the use case: projecting columns that don't have bad defaults, writing to files where the column is always provided so default is never needed, etc.. I'm raising this as this feels to be heading in the opposite direction of other changes, like validating construction of types allowing them only to be constructed or deserialized if they are valid. I'm wondering what your take is here. -- 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]
