LuciferYang opened a new issue, #13435: URL: https://github.com/apache/gravitino/issues/13435
### Version main branch ### Describe what's wrong When force-dropping a metalake, `MetalakeManager.dropCatalogsUnderMetalake` temporarily re-enables a user-disabled metalake so `CatalogManager.dropCatalog` accepts the child cleanup. If that cleanup fails (a catalog drop or a store error), the exception propagates while the metalake is left enabled, and its child catalogs are partially dropped. This silently undoes the disable the user asked for. ### How to reproduce 1. Disable a metalake. 2. Force-drop it, with a failure during child-catalog cleanup (for example a catalog whose drop fails). 3. The drop aborts, but the metalake is now enabled again instead of staying disabled. -- 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]
