Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *created* an issue
Hibernate ORM (
https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTE0NDc5NjZl...
) / Improvement (
https://hibernate.atlassian.net/browse/HHH-16546?atlOrigin=eyJpIjoiNTE0ND...
) HHH-16546 (
https://hibernate.atlassian.net/browse/HHH-16546?atlOrigin=eyJpIjoiNTE0ND...
) Reduce verbosity of logs in a few edge cases (
https://hibernate.atlassian.net/browse/HHH-16546?atlOrigin=eyJpIjoiNTE0ND...
)
Issue Type: Improvement Assignee: Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) Components: hibernate-core Created: 03/May/2023 06:07 AM Fix Versions: 6.2.3 Priority:
Major Reporter: Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
)
There are a few INFO logs that really should be debug logs, because they don’t bring
useful information to users and/or represent normal operation.
In particular, on startup:
* org.hibernate.internal.CoreMessageLogger#lazyPropertyFetchingAvailable : “Lazy property
fetching available for <property name>“. This appears as soon as we annotate a
property with @Basic(fetch = LAZY) , and I don’t think it’s necessary to remind the user
of their mapping.
And worse, at runtime:
* org.hibernate.internal.CoreMessageLogger#handlingTransientEntity : "Handling
transient entity in delete processing": apparently this behavior was added to comply
with JPA spec. Why would we log at info level that we’re complying with JPA every time a
transient entity is passed to delete? It may be weird, but if it’s according to spec… ?
(
https://hibernate.atlassian.net/browse/HHH-16546#add-comment?atlOrigin=ey...
) Add Comment (
https://hibernate.atlassian.net/browse/HHH-16546#add-comment?atlOrigin=ey...
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira....
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100224- sha1:4684446 )