LuciferYang commented on PR #13225:
URL: https://github.com/apache/gravitino/pull/13225#issuecomment-5698312829

   The check-then-delete window is real and is documented in the method's 
Javadoc as a best-effort, non-atomic rollback. This is a default interface 
method with no transaction or locking primitive available at this layer, so a 
truly atomic compare-and-delete is not expressible here. The rollback 
deliberately deletes the model only when it still has zero versions, so it will 
not remove a model that another actor concurrently linked a version to; the 
original exception is always the one rethrown. Documenting the limitation 
rather than over-promising atomicity is the intended behavior.
   


-- 
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]

Reply via email to