snazy commented on issue #3008: URL: https://github.com/apache/polaris/issues/3008#issuecomment-3510200523
Thanks @adam-christian-software, this is a request for a missing functionality in Polaris, so the request for this is totally legit and valid! Catalogs can have a huge amount of namespaces, catalog-roles and tables and views. Just considering that quite an amount of backend database operations is necessary for this use case, and that database operations may stall or block (e.g. tx sync) or fail (e.g. tx deadlock), a whole catalog-purge operation has to be asynchronous and also resumable. On top, as a drop-catalog-purge can easily take a long time, the catalog must not be usable for others while it is being purged. This requires a catalog-state-management and a corresponding catalog-state-machine. Cross-catalog references are risky, and this use case is one example why. Circular cross-catalog references would be a blocker. -- 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]
