Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug report] Gravitino REST Server Defaults to 'jdbc' Instead of Using Catalog Name from Spark Configuration #6310

Open
dataageek opened this issue Jan 17, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@dataageek
Copy link

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:

./spark-sql \
    --conf spark.sql.catalog.iceberg_jdbc_catalog=org.apache.iceberg.spark.SparkCatalog \
    --conf spark.sql.catalog.iceberg_jdbc_catalog.warehouse="/mnt/c/iceberg-warehouse" \
    --conf spark.sql.catalog.iceberg_jdbc_catalog.type=rest \
    --conf spark.sql.catalog.iceberg_jdbc_catalog.uri=http://127.0.0.1:9991/iceberg \
    --conf spark.sql.extensions=org.apache.iceberg.spark.extensions.IcebergSparkSessionExtensions

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

@dataageek dataageek added the bug Something isn't working label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant