officialtushark commented on issue #8254: URL: https://github.com/apache/iceberg/issues/8254#issuecomment-1669646731
Thanks @nastra. I did see this test case demonstrating the behaviour. However I could not wrap my head around the reasoning for this. At one hand, I do understand a conflicting schema change (`t1 adds a col1:int and t2 adds a col1:double`) should trigger a failure . However, In case when there is non-conflicting change to the schema(`t1 add col1:int, t2 also adds col1:int`), why do we resort to fail the transaction? -- 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]
