lasdf1234 opened a new issue, #13151: URL: https://github.com/apache/gravitino/issues/13151
### Version branch-1.3 ### Describe what's wrong After [#12750](https://github.com/apache/gravitino/issues/12750) / [#12751](https://github.com/apache/gravitino/pull/12751), JDBC catalogs return `jdbc-user` in plaintext because it identifies the account rather than a secret. Iceberg and Paimon JDBC backends on `branch-1.3` still mark `jdbc-user` as `hidden`, so `GET .../catalogs/{catalog}` returns `******` for Iceberg/Paimon while JDBC returns the real username. This is fixed on `main` by #13124 / #13125. Cherry-pick it to `branch-1.3`. ### Error message and/or stacktrace Iceberg/Paimon catalog properties response shows: ```json "jdbc-user": "******" ``` while a JDBC catalog with the same username shows: ```json "jdbc-user": "demo" ``` ### How to reproduce 1. Create a JDBC catalog with `jdbc-user` / `jdbc-password`. 2. Create a `lakehouse-iceberg` catalog with `catalog-backend=jdbc` and the same `jdbc-user` / `jdbc-password`. 3. Load both catalogs via the REST API on a 1.3 server. 4. Observe that JDBC returns plaintext `jdbc-user`, while Iceberg returns `******`. ### Additional context Align Iceberg and Paimon with the JDBC behavior from #12750. Keep `jdbc-password` and cloud credential secrets hidden/masked. Related: #13124, #13125 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
