You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have multiple catalogs created using the Iceberg JDBC catalog. When I attempt to consume these catalogs via the Gravitino REST server (using the REST catalog through Spark), the implementation always defaults to using jdbc as the catalog name instead of the catalog name specified in the Spark configuration.
I expect Spark to use the iceberg_jdbc_catalog catalog, as specified in the configuration. However, the Gravitino REST server implementation instead looks for a catalog named jdbc.
Although I can override this behavior using the catalog-backend-name property in gravitino.conf, I would prefer a dynamic mechanism that fetches the catalog name from the Spark configuration directly.
Error message and/or stacktrace
No error message. just not working as expected
How to reproduce
0.7.0
Additional context
No response
The text was updated successfully, but these errors were encountered:
Version
main branch
Describe what's wrong
I have multiple catalogs created using the Iceberg JDBC catalog. When I attempt to consume these catalogs via the Gravitino REST server (using the REST catalog through Spark), the implementation always defaults to using jdbc as the catalog name instead of the catalog name specified in the Spark configuration.
For example, when running the following command:
I expect Spark to use the iceberg_jdbc_catalog catalog, as specified in the configuration. However, the Gravitino REST server implementation instead looks for a catalog named jdbc.
Although I can override this behavior using the catalog-backend-name property in gravitino.conf, I would prefer a dynamic mechanism that fetches the catalog name from the Spark configuration directly.
Error message and/or stacktrace
No error message. just not working as expected
How to reproduce
0.7.0
Additional context
No response
The text was updated successfully, but these errors were encountered: