s4ravanan opened a new pull request, #13508: URL: https://github.com/apache/gravitino/pull/13508
### What changes were proposed in this pull request? - In `JdbcCatalogOperations.loadSchema`, downgrade the log level from `WARN` to `DEBUG` when a loaded schema's comment does not carry a Gravitino identifier. - Remove user comment text interpolation from the log message to avoid leaking user comment text into logs, and log the schema identifier instead. - Added unit tests covering schema loading without an identifier, with an identifier, and with a null comment in `TestJdbcCatalogOperations`. ### Why are the changes needed? For JDBC catalogs whose underlying databases cannot or deliberately do not store Gravitino identifiers in schema comments, `StringIdentifier.fromComment(comment)` returning `null` is expected and handled by `SchemaOperationDispatcher` falling back to the entity store. Emitting a `WARN` on every schema load created unnecessary log noise and interpolated user comment text into the logs. Fix: #13434 ### Does this PR introduce _any_ user-facing change? No API changes. The log level for schemas without Gravitino IDs in comments is reduced from `WARN` to `DEBUG`, and user comments are no longer logged. ### How was this patch tested? - Added `testLoadSchemaWithoutGravitinoId`, `testLoadSchemaWithNullComment`, and `testLoadSchemaWithGravitinoId` in `TestJdbcCatalogOperations`. - Ran `./gradlew :catalogs:catalog-jdbc-common:test -PskipITs -PskipDockerTests=true`. -- 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]
