yuqi1129 opened a new issue, #13695: URL: https://github.com/apache/gravitino/issues/13695
### Describe the subtask The `metadataIdCache` key prefix of a metalake is `<ml>␟METALAKE␟`. Keys of catalogs, tags, policies and other objects start with `<ml>␟CATALOG␟…`, `<ml>␟TAG␟…` and so on, so prefix invalidation of the metalake key does not reach them. `MetalakeHookDispatcher.dropMetalake` does not call `notifyEntityNameIdMappingChange` either, and the change log only records a single METALAKE DROP. As a result, after a metalake is force-dropped and recreated with same-named children, both the local node and peer nodes authorize against the old IDs until the cache TTL expires. Proposed fix: when a metalake is dropped, evict every key under the `<ml>␟` prefix, both in the local hook and in peer change-log replay. Add unit tests. ### Parent issue #13303 -- 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]
