rdblue commented on PR #5230: URL: https://github.com/apache/iceberg/pull/5230#issuecomment-1200274162
> > They are intended for information to configure reading or writing a table. > > Time to evolve? :) I think this is a great demonstration of why we want to be strict. This would be a convenient place to stash properties, but then you run into situations like this one where properties don't provide the behavior guarantees that you want for another use case. If we think about implementing those behaviors, then we need to consider things like how to make assertions on the state of table properties in the REST API so that concurrent updates will fail and the client can retry. That's a lot of work and it makes the REST spec more difficult to implement. I think it is best to continue with the current behavior, especially given that there is a reasonable work-around. -- 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]
