Allow dynamically setting the log level even for loggers that aren't already explicitly configured #13156
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.
root
,org.apache.pinot.tools.admin
andorg.reflections
(see this log4j config file for reference).org.apache.pinot.controller.helix.core.realtime.SegmentCompletionManager
class viaPUT /loggers/org.apache.pinot.controller.helix.core.realtime.SegmentCompletionManager?level=DEBUG
, this returns the following response:{"code":500,"error":"Logger - org.apache.pinot.controller.helix.core.realtime.SegmentCompletionManager not found"}
In a future enhancement, we could also allow dynamically setting the log level for an ancestor logger which would affect all the descendant loggers (see https://logging.apache.org/log4j/2.x/manual/architecture.html#logger-hierarchy).org.apache.pinot.controller.helix.core
. This will then also affect the log level for all the descendant / child loggers - for instance,org.apache.pinot.controller.helix.core.realtime.SegmentCompletionManager
(see https://logging.apache.org/log4j/2.x/manual/architecture.html#logger-hierarchy).bugfix
orfeature