Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kazuki43zoo I don't really see any savings in this specific one. I understand the prior want to check for debug since there is an otherwise expensive looping on logging. However, that isn't the case here. I don't think this is going to amount to much in savings. Am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @hazendaz , thanks for your comment.
In this case, your understanding and opinion is correct.
However, i think general coding style to use the
isDebugEnablemethod when debug message is dynamically.What do you think ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would agree if the logging hit was needed and generally I see string format in a logger as bad practice. After looking at the class a bit, I see an obvious flaw in logging being used. It's using apache commons logging (legacy) but also has slf4j available. If we switched this to use slf4j instead, the cost can be incurred inside the debug statement rather than external to it. However, that is beyond this pull request so for the time being this is ok. I'm merging it now. Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for merging !!
I agree with your opinion 👍