yuqi1129 opened a new issue, #12576: URL: https://github.com/apache/gravitino/issues/12576
### What would you like to be improved? Schema deletion currently materializes complete child metadata objects only to determine whether a schema is empty. Because this check runs while holding the catalog/schema delete fence, large schemas can keep the lock longer than necessary. Schema-scoped services also repeat the parent-lock transaction pattern. A future schema child type could accidentally write without taking the parent fence in the same transaction. ### How should we improve? - Replace full child PO loading in the schema emptiness check with lightweight existence queries. - Provide one schema-scoped transaction entry point that acquires the parent schema lock and executes the child writes in the same transaction. - Migrate table, view, fileset, function, model, model version, and topic writes to the shared entry point. - Cover the SQL and real service paths on H2, MySQL, and PostgreSQL. Follow-up to #12456. -- 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]
