yuqi1129 opened a new issue, #13434:
URL: https://github.com/apache/gravitino/issues/13434
### What would you like to be improved?
`JdbcCatalogOperations.loadSchema` logs a WARN on every schema load whose
source comment carries no Gravitino identifier:
```java
StringIdentifier id = StringIdentifier.fromComment(comment);
if (id == null) {
LOG.warn("The comment {} does not contain Gravitino id attribute",
comment);
return load;
}
```
This is the normal path, not an anomaly, for every JDBC catalog whose source
cannot store the identifier in a schema comment, or that deliberately does not
write it there. `SchemaOperationDispatcher` handles the null-id case by
resolving the schema through the entity store, so nothing is wrong when the
WARN fires.
Two problems:
1. Every schema read on such a catalog emits a WARN, so the level does not
reflect the severity and the noise hides real warnings.
2. The message interpolates the schema comment, which is user-authored text,
into the log.
### How should we improve?
Downgrade this to DEBUG, or skip it for catalogs that are known not to store
the identifier in the comment, so the entity-store fallback stays silent on the
path where it is expected.
--
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]
