jarredhj0214 opened a new pull request, #13562: URL: https://github.com/apache/gravitino/pull/13562
### What changes were proposed in this pull request? - Add an optional `includeProperties` parameter to the catalog list REST API. - Add corresponding Java client and catalog API overloads. - Propagate the option through the catalog dispatcher chain. - Avoid resolving catalog properties and initializing server-side catalog wrappers when the option is disabled. - Let the Spark connector request lightweight descriptors during startup. - Load and cache complete catalog information when a catalog is first used. - Keep lightweight descriptors separate from the complete, identity-aware catalog cache. ### Why are the changes needed? Spark requires top-level V2 catalog names to be registered before SQL analysis, so the connector must still discover visible catalogs during driver startup. However, startup registration only requires each catalog’s name, type, and provider. Resolving properties for every catalog causes unnecessary catalog initialization and makes startup slow when a metalake contains many catalogs. Fix: #13561 ### Does this PR introduce _any_ user-facing change? Yes. - The catalog list REST API accepts the optional `includeProperties` query parameter when `details=true`. - The Java client provides `listCatalogsInfo(boolean includeProperties)`. - The default value is `true`, so existing callers retain the original behavior. ### How was this patch tested? - `./gradlew :core:test --tests org.apache.gravitino.catalog.TestCatalogManager` - `./gradlew :core:test --tests org.apache.gravitino.listener.api.event.TestCatalogEvent` - `./gradlew :server:test --tests org.apache.gravitino.server.web.rest.TestCatalogOperations` - `./gradlew :clients:client-java:test --tests org.apache.gravitino.client.TestGravitinoMetalake` - `./gradlew :spark-connector:spark-3.5:test --tests org.apache.gravitino.spark.connector.catalog.TestGravitinoCatalogManager` - `./gradlew :docs:build` - `./gradlew spotlessApply` -- 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]
