You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2019/06/11 04:15:00 UTC
[jira] [Resolved] (ACCUMULO-3680) Remove / deprecate use of log4j
setLevel to dynamically control logging
[ https://issues.apache.org/jira/browse/ACCUMULO-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Tubbs resolved ACCUMULO-3680.
-----------------------------------------
Resolution: Fixed
Deprecated in 2.0
> Remove / deprecate use of log4j setLevel to dynamically control logging
> -----------------------------------------------------------------------
>
> Key: ACCUMULO-3680
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3680
> Project: Accumulo
> Issue Type: Sub-task
> Components: build
> Reporter: Christopher Tubbs
> Priority: Major
> Fix For: 2.0.0
>
>
> Logging should be configurable by users, who control log behavior using their desired log appenders and log configuration. We should not be making decisions in code which affect which items are logged. We should just send the information to the logger to let it make that decision.
> This is also unsupported by slf4j, which gives users better control over their logging.
> As such, we should remove (and deprecate, as needed) code which alters the log level dynamically.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)