[
https://issues.apache.org/jira/browse/ACCUMULO-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483814#comment-14483814
]
Bob Thorman commented on ACCUMULO-3652:
---------------------------------------
There are several place in the core and shell that set the logging level during
runtime which slf4j does not support. Example from
o.a.a.core.client.mapred.AbstractInputFormat
log.setLevel(logLevel);
Does anybody have an idea how to refactor this with using slf4j? I've seen
some hacks mentioned online but nothing looks enduring.
> Remove string concatenation in log statements where slf4j is used.
> ------------------------------------------------------------------
>
> Key: ACCUMULO-3652
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3652
> Project: Accumulo
> Issue Type: Sub-task
> Components: build
> Affects Versions: 1.7.0
> Reporter: Ed Coleman
> Assignee: Bob Thorman
> Priority: Minor
> Fix For: 1.8.0
>
>
> As a separate task, continue with the conversion to remove log4j
> dependencies, modify log statements where string concatenation is used and
> replace with {} parameter substitution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
