GitHub user jonsnowseven added a comment to the discussion: Iceberg Catalogs & S3 access
> what do you mean about create the respective catalogs, IRC supports static > and dynamic catalog providers. Let's say I have a **dynamic catalog providers enabled**. When I create multiple catalogs with different backends (using the Gravitino Catalog API), dynamic catalog providers feature will poll these catalogs and register them in Iceberg REST server side so they will be accessible in downstream processes through Iceberg REST? Now let's say I have **static catalog providers enabled**. If I have the following: ``` gravitino.iceberg-rest.catalog-backend = jdbc gravitino.iceberg-rest.uri = jdbc:postgresql://127.0.0.1:5432 gravitino.iceberg-rest.warehouse = hdfs://127.0.0.1:9000/user/hive/warehouse-postgresql ... gravitino.iceberg-rest.catalog.hive_backend.catalog-backend = hive gravitino.iceberg-rest.catalog.hive_backend.uri = thrift://127.0.0.1:9084 gravitino.iceberg-rest.catalog.hive_backend.warehouse = /user/hive/warehouse-hive/ ... gravitino.iceberg-rest.catalog.jdbc_backend.catalog-backend = jdbc gravitino.iceberg-rest.catalog.jdbc_backend.uri = jdbc:mysql://127.0.0.1:3306/ gravitino.iceberg-rest.catalog.jdbc_backend.warehouse = hdfs://127.0.0.1:9000/user/hive/warehouse-mysql ... ``` When I launch Gravitino server, what is the effect of having the previous configuration? > There is a flag to control whether to initialize the JDBC backend Does this flag apply to **all** backends? GitHub link: https://github.com/apache/gravitino/discussions/9663#discussioncomment-15483304 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
