pvary commented on issue #14096: URL: https://github.com/apache/iceberg/issues/14096#issuecomment-3347803441
> I will also note, this is exacerbated by `hive.stats.autogather`, as if there is a large delay in gathering stats, the more commits can be committed before the initial rogue alter_table succeeds, and the more data loss can occur. I remember that we turned off the stats gathering when we did the Hive integration. So to summarize: - We know that the client is capable to send the EnvironmentContext as an input for every version of the supported HMS service - If we enable the context based concurrency handling is always embedded into the lock based concurrency handling (if both are used), and using the EnvironmentContext doesn't lock anything, I don't see the possibility of a dead lock. - We need to check if anything important (error handling, or something else) is dependent on the lock settings If everything checks out, then we could proceed with enabling sending the environment context content in every call. -- 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]
