-
Notifications
You must be signed in to change notification settings - Fork 15.4k
KAFKA-10469: Resolve logger levels hierarchically #9266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ijuma
merged 9 commits into
apache:trunk
from
tombentley:KAFKA-10469-resolve-logger-levels
Sep 30, 2020
+45
−7
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
2272bf3
KAFKA-10469: Resolve logger levels hierarchically
tombentley 3b75b0b
Fix logic & move test
tombentley 9fe8c46
comment
tombentley 814431e
make private
tombentley dbeead9
Assert
tombentley 9110d76
Remove com.typesafe.scalalogging.Logger
tombentley 6310c03
Fix infinite loop
tombentley 42ddf73
Fix test
tombentley a4ec843
Review comment
tombentley File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
@tombentley A small propsal: would
org.apache.log4j.Level.TRACE.toStringbe better?It passes compilation checks.
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.
@dongjinleekr that would be fine for the
setLogLevel()andassertEqualscalls, but there would still be the level name in theassertTrue(...contains("kafka=TRACE"))calls. I think fixing it there would make the code harder to read, and given that the declaration ofTRACEis in an external API on which we depend, and the name will not change there doesn't seem to be any benefit to using the declaration rather than the name as a literal.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.
@tombentley Great. Your stance is reasonable. I am convinced.