[
https://issues.apache.org/jira/browse/APEXCORE-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601132#comment-15601132
]
Priyanka Gugale commented on APEXCORE-564:
------------------------------------------
Our initial though was, we will set it to NULL so that either parent or root
level logger will be picked up. As you explained patters are cumulative so
taking example of com.datatorrent.engine.*, say following levels were set
earlier
com.datatorrent.engine.*=INFO
com.datatorrent.engine.*=DEBUG
Now to remove it, as LoggerUtil doesn't have a way to remove these patterns, we
though of setting ti to null so now entries look like
com.datatorrent.engine.*=INFO
com.datatorrent.engine.*=DEBUG
com.datatorrent.engine.*=null
After doing the logger level for com.datatorrent.engine.* will either be picked
from parent pattern say com.datatorrent.* or from root logger. That was our
understanding. Also after this if someone wishes to set some new level on
logger that is also feasible.
Please let us know if this approach looks good?
> We should be able to remove loggers level settings
> --------------------------------------------------
>
> Key: APEXCORE-564
> URL: https://issues.apache.org/jira/browse/APEXCORE-564
> Project: Apache Apex Core
> Issue Type: New Feature
> Reporter: Priyanka Gugale
> Assignee: Priyanka Gugale
> Priority: Minor
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> StramWebServices has api to setLoggersLevel, but there is not way to remove
> the already set loggers level. There should be an api to remove loggers level
> which was set earlier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
