Closed niyushabaghayi closed 4 weeks ago
@LauraXia123 would you please help to review this PR?
@niyushabaghayi hi, the latest commit have no issue about #5440 , let me know if you have any problems after retesting!
Thanks, @LauraXia123! Could you please point me to the specific issue and related PR that resolved this problem? I tried searching but couldn't find it, and I'm still experiencing the issue on the latest version (Gravitino 0.6.1-incubating). Any guidance would be greatly appreciated!
Fixed on (Gravitino 0.7.0-incubating), you can retry it on main branch or tag (v0.7.0-incubating-rc2). You can find the dup issue: https://github.com/apache/gravitino/issues/5328
Why are the changes needed? These changes are needed to address a bug in the Gravitino UI that prevents users from successfully creating a catalog with
type: relational
andprovider: Apache Iceberg
. The missing properties cause a 400 error on the backend, blocking catalog creation.Fix: #5440
Does this PR introduce any user-facing change? Yes, this PR allows users to create catalogs with
type: relational
andprovider: Apache Iceberg
without encountering a 400 error due to missing JDBC properties. It resolves the issue of incomplete payloads and improves catalog creation reliability.How was this patch tested?
Manual Testing:
type
torelational
,provider
toApache Iceberg
, and configuredcatalog-backend
asjdbc
with appropriatejdbc-driver
,jdbc-user
, andjdbc-password
values.Steps to Test: Follow the reproduction steps outlined in the issue report to confirm that the changes address the problem.
Edge Cases: Tested with
catalog-backend
set tojdbc
and verified correct behavior.