yuqi1129 opened a new issue, #13632: URL: https://github.com/apache/gravitino/issues/13632
### Describe the subtask **Priority:** P3 (G7) **Problem:** Some invariants span several entities and cannot be expressed with single-entity store calls: metalake in-use propagation updates the metalake and each catalog separately (M5), and replacing a stale registration takes a delete and a separate insert (#13198). A failure or a concurrent writer between the steps leaves them inconsistent. **Scope:** Depending on the P0-3 decision, either support such invariants through the store, or remove the need for them, for example by deriving a catalog's effective in-use state from its metalake at read time. Record which invariants remain non-atomic and why that is acceptable. ### 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]
