deniskuzZ commented on PR #5567: URL: https://github.com/apache/hive/pull/5567#issuecomment-2517067831
> > I am not sure I get this. There is already a table-level lock for atomic stats update and we are adding an extra re-try loop inside? > > The existing table-level lock is an in-memory lock. That means in case you have multiple HMS instances and two different processes are getting requests in the same time, it just doesn't have any effect - as on JVM level, there is only one single instance. ok, in-memory lock serves diff purpose - thread safety, see HIVE-25904. Descriptions says "updateTableColumnStatistics can throw SQLIntegrityConstraintViolationException during replication if HA is on and two different HMS instance gets the same call but with different engine. " isn't the engine part of PK? RawStore interface. methods are not retriable -- 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]
