yuqi1129 opened a new issue, #14501: URL: https://github.com/apache/gravitino/issues/14501
### Version main branch ### Describe what's wrong After a native schema is dropped/recreated with a different source ID, overwrite can collide with or retain the stale name registration and its old descendants/associations. Schema/table create also catches entity-store registration failure after the catalog create succeeds and returns a successful response. ### Error message and/or stacktrace A successful create response can conceal a failed Gravitino registration. A recreated schema can resolve to a stale ID, retain old children or fail with a relational unique-key conflict. ### How to reproduce 1. Import a schema and a child table, with governance associations. 2. Recreate the source schema with the same name and a new source ID. 3. Register the replacement and inspect its ID and old descendants. 4. Separately inject an entity-store put failure after successful catalog schema/table creation and inspect the create response. ### Additional context Replacement should retire stale relational metadata atomically, preserve same-ID children and concurrent/cross-catalog identities, and surface partial-success failures with cause and recovery guidance. Related broad reconciliation work: #13313; this is a write-triggered repair, not a periodic reconciler. -- 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]
