ajantha-bhat commented on PR #6789: URL: https://github.com/apache/iceberg/pull/6789#issuecomment-1436494627
> I think so. This issue is not specific to this PR. I just think this PR makes it more likely to manifest. Would it be possible to keep the "expected" hash at the Tx level? @dimas-b : In that case, txn can only commit one successful commit? > Sure this does not break the expected-hash calculations for commits? @snazy: can you please elaborate on this? Without this PR also, concurrent commits from the same client can refresh the catalog and cause breakage of expected-hash. a) Are you suggesting that this PR will increase the probability of that event happening and we don't want to do that? b) Even the sequential updates have issues mentioned in the PR description and I want to fix them. Should I keep the changes only for `listTables(), listNamespaces(), loadNamespaceMetadata(), setProperties(), removeProperties()`? -- 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]
