yuqi1129 opened a new issue, #13627: URL: https://github.com/apache/gravitino/issues/13627
### Describe the subtask **Priority:** P2 (G3) **Problem:** Lifecycle conditions are checked in managers before the store call, so they can be invalidated before the write: a non-force catalog or metalake drop can still delete a child created after its emptiness check (#13176), and a child can be written under a parent that is concurrently disabled or no longer in use. The store only offers a `cascade` flag, so each new condition turns into a special method. **Scope:** Design how such conditions are decided together with the write they guard, without exposing locks or versions at the interface: non-force drops that allow known children, in-use/enabled checks for child writes, and a DELETING state for force drops. Move #13176 onto it and remove `SupportsConditionalCatalogDelete`. ### Parent issue #13621 -- 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]
