yuqi1129 opened a new pull request, #13499: URL: https://github.com/apache/gravitino/pull/13499
### What changes were proposed in this pull request? - Check non-force metalake deletion for child catalogs inside the store transaction. - Check non-force catalog deletion for child schemas inside the store transaction. Preserve the existing handling of built-in, imported, and externally removed schemas by allowing only the schema IDs classified before deletion. - Cover late schema creation, rollback, cache invalidation, and change-log emission. ### Why are the changes needed? A child created after the manager's emptiness check could previously be removed by the subsequent cascade delete. The transactional check rejects that deletion instead. Related to #13176. The metalake in-use fan-out and force-drop lifecycle remain follow-up work. ### Does this PR introduce _any_ user-facing change? Yes. A non-force drop now rejects a concurrently created child rather than silently deleting it. No API or configuration changes. ### How was this patch tested? - `:core:test` for `TestCatalogManager`, `TestMetalakeManager`, `TestRelationalEntityStore`, `TestCatalogMetaService`, `TestMetalakeMetaService`, and `TestEntityChangeLogService` with H2. - `:core:spotlessApply` and `git diff --check`. -- 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]
