You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2015/12/02 17:55:10 UTC
[jira] [Commented] (SOLR-8359) Restrict child classes from using
parent logger's state
[ https://issues.apache.org/jira/browse/SOLR-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036117#comment-15036117 ]
Mike Drob commented on SOLR-8359:
---------------------------------
[~gerlowskija] - do you want to take a look at this? I didn't notice it missing when looking at the original patch, but it looks like a pretty straightforward fix.
> Restrict child classes from using parent logger's state
> -------------------------------------------------------
>
> Key: SOLR-8359
> URL: https://issues.apache.org/jira/browse/SOLR-8359
> Project: Solr
> Issue Type: Sub-task
> Reporter: Mike Drob
> Fix For: Trunk
>
>
> In SOLR-8330 we split up a lot of loggers. However, there are a few classes that still use their parent's logging state and configuration indirectly.
> {{HdfsUpdateLog}} and {{HdfsTransactionLog}} both use their parent class cached read of {{boolean debug = log.isDebugEnabled()}}, when they should check their own loggers instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org