pvary commented on issue #6370: URL: https://github.com/apache/iceberg/issues/6370#issuecomment-1369791961
@dmgcodevil: It turns out you have been right. Even though we do the changes in transaction on HMS side, the isolation level we use for those changes is `READ_COMMITTED`. This does not prevent reading old data and writing out the new ones concurrently. Thanks for the feedback! I updated the Hive PR to use `REPEATABLE_READ` which would prevent the situation and act as a lock for our case. -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
