yuqi1129 opened a new issue, #12451: URL: https://github.com/apache/gravitino/issues/12451
### Describe the subtask Add database-backed optimistic concurrency control and transaction boundaries for metalake writes. - Advance the metalake OCC version on every alter, and guard alter and delete with a compare-and-set on the observed version. - Classify a failed CAS as either a stale-version conflict or an already-missing entity. - Keep the root CAS, the non-empty check or the cascade cleanup, and the change-log writes in one database transaction. - Lock the catalog rows before a cascade snapshot, then CAS-delete descendant catalogs and schemas with their observed identifier-and-version pairs. - Add the shared `OptimisticLockException` factories reused by the catalog and schema subtasks. Split out of #12350 to keep each review small. First of three: metalake -> catalog -> schema. ### Parent issue https://github.com/apache/gravitino/issues/12342 -- 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]
