When creating a catalog with type: relational and provider: Apache Iceberg, the Gravitino UI fails to include the jdbc-driver, jdbc-user, and jdbc-password parameters in the request payload. As a result, the backend returns a 400 error, indicating that jdbc-driver is null and invalid.
Error message and/or stacktrace
The error message displayed in the UI is as follows:
AxiosError: Request failed with status code 400
null in jdbc-driver is invalid. The value can't be blank
How to reproduce
Go to the Gravitino UI and open the "Create Catalog" dialog.
Set the following values:
Name: [whatever you want]
Type: relational
Provider: Apache Iceberg
Under the "Properties" section, set the following:
catalog-backend: jdbc
uri: jdbc:postgresql://[host]:[port]/[db]
warehouse: s3://[bucket]/[prefix]
jdbc-driver: org.postgresql.Driver
jdbc-user: [username]
jdbc-password: [password]
Click on "Create."
Observe the 400 error in the console or the UI error message:
- null in jdbc-driver is invalid. The value can't be blank
Version
main branch
Describe what's wrong
When creating a catalog with type:
relational
andprovider: Apache Iceberg
, the Gravitino UI fails to include thejdbc-driver
,jdbc-user
, andjdbc-password
parameters in the request payload. As a result, the backend returns a 400 error, indicating thatjdbc-driver
isnull
and invalid.Error message and/or stacktrace
The error message displayed in the UI is as follows:
AxiosError: Request failed with status code 400
null in jdbc-driver is invalid. The value can't be blank
How to reproduce
Go to the Gravitino UI and open the "Create Catalog" dialog.
Set the following values:
relational
Apache Iceberg
Under the "Properties" section, set the following:
catalog-backend
:jdbc
uri
:jdbc:postgresql://[host]:[port]/[db]
warehouse
:s3://[bucket]/[prefix]
jdbc-driver
:org.postgresql.Driver
jdbc-user
: [username]jdbc-password
:[password]
Click on "Create."
Observe the 400 error in the console or the UI error message:
- null in jdbc-driver is invalid. The value can't be blank
Additional context
No response