Replace the complex lazy mechanism for dropping tables/schemas, which defers the resource cleanup to a VACUUM command, with eager deletion using the bulk deletion API in object_store.
For now keep the repository API and try to purge any remaining entries on startup, so that we can perform the migration (i.e. drop the dropped_tables catalog table) on the next minor release. This will greatly simplify the new TableStore interface.
Replace the complex lazy mechanism for dropping tables/schemas, which defers the resource cleanup to a VACUUM command, with eager deletion using the bulk deletion API in object_store.
For now keep the repository API and try to purge any remaining entries on startup, so that we can perform the migration (i.e. drop the
dropped_tablescatalog table) on the next minor release. This will greatly simplify the newTableStoreinterface.