lasdf1234 opened a new issue, #14324: URL: https://github.com/apache/gravitino/issues/14324
### What would you like to be improved? For maintenance policies attached to a **catalog** or **schema**, policy-expand currently enumerates tables only from Gravitino `table_meta` / `schema_meta`. Tables that exist in the underlying Iceberg catalog (jdbc/hive/rest) but are not yet registered in Gravitino are skipped. ### How should we improve? 1. When expanding catalog/schema-scoped policy attachments, call `SchemaDispatcher.listSchemas` / `TableDispatcher.listTables` (via `IcebergCatalogOperations` underneath). 2. For each name, `loadSchema` / `loadTable` so missing entities are **imported** into the store (existing import path in operation dispatchers). 3. Then run nearest-policy / occupancy gating as today. 4. **Non-goals:** do not borrow aux IRC1 `CatalogWrapperManager` in-process; lakehouse keeps its own backends (jdbc/hive; rest remains HTTP). Direct table-tagged policies stay on the meta path. -- 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]
