yuqi1129 opened a new issue, #13475: URL: https://github.com/apache/gravitino/issues/13475
### Version main branch ### Describe what's wrong Dropping an unmanaged catalog registration can leave external schemas and tables in place with their `gravitino.identifier` still stored in properties or comments. Recreating the catalog then imports stale IDs. #13197 temporarily handles soft-deleted metadata rows, but the external identifiers remain. ### Error message and/or stacktrace Before the temporary fix, reimport could fail with an ID conflict against a soft-deleted metadata row. ### How to reproduce 1. Register an external catalog and load a schema and table so they receive Gravitino identifiers. 2. Drop the catalog with force while the external objects remain. 3. Inspect their properties or comments: the identifiers are still present. 4. Recreate the catalog and load the same objects. ### Additional context When a catalog is detached, clear matching Gravitino identifiers from external objects that remain. Cover connectors that store IDs in properties or comments, and define the behavior when external cleanup fails. -- 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]
