Skip to content

Conversation

@diegolovison
Copy link
Contributor

@diegolovison diegolovison commented May 29, 2025

HHH-19491 Improve trace logs to reduce the effort while troubleshooting issues with dirty entities


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.


https://hibernate.atlassian.net/browse/HHH-19491

* a no-op.
*/
Object processEntity(Object value, EntityType entityType) throws HibernateException {
Object processEntity(Object entity, Object value, EntityType entityType) throws HibernateException {

Check notice

Code scanning / CodeQL

Useless parameter Note

The parameter 'entity' is never used.
* a no-op.
*/
Object processEntity(Object value, EntityType entityType) throws HibernateException {
Object processEntity(Object entity, Object value, EntityType entityType) throws HibernateException {

Check notice

Code scanning / CodeQL

Useless parameter Note

The parameter 'entityType' is never used.
@gavinking
Copy link
Member

Honestly I'm not particularly keen on adding more trace-level logging. Not sure how others feel about it.

@diegolovison
Copy link
Contributor Author

Hi @gavinking

See https://hibernate.atlassian.net/browse/HHH-19495
Without those traces, it is like impossible to track what is going on.

@gavinking
Copy link
Member

Yes I understand that these trace messages helped you find the source of that problem.

But when is the next time someone will find them useful?

Imagine if we committed new trace-level messages every time we needed them to solve a bug. The source code would be overflowing with them.

@diegolovison
Copy link
Contributor Author

Right, I don't have a strong opinion.
If you or the team decides that we can close without merge, I am happy with it.

@gavinking
Copy link
Member

Let's see what others think.

@mbellade
Copy link
Member

I would agree with @gavinking, these logs seem a bit too verbose, especially ones triggered for each property of an entity, and would only be useful in very specific troubleshooting scenarios. If we could improve an existing log with more/better information maybe that would be ok.

@diegolovison
Copy link
Contributor Author

Ok. Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants