[ 
https://issues.apache.org/jira/browse/ACCUMULO-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902040#comment-13902040
 ] 

Christopher Tubbs commented on ACCUMULO-2349:
---------------------------------------------

[~vickyuec]: Agreed that these changes are major and should not be done in 
older versions. This ticket is marked for 1.7, though. If this ticket is about 
making loud complaints about a missing file in 1.7, then I think these 
alternatives which have been suggested are a preferable way to go.

Further, if we agree that these alternatives (specifically, dropping the 
*_logger.xml files) are something we're going to do in a future version, then 
we need to keep that in mind in "fixing" previous releases. We don't want to 
create churn by tolerating missing files in one version, complaining very 
loudly about those missing files in the next bugfix version, and then not using 
those files at all in the next version.

With that in mind, the correct solution for the current problem in previous 
releases seems to me to be that we should not complain loudly. Rather, we 
should find ways to be more tolerant of those missing files, without 
complaining to users and demanding they take action. Hence [my suggestion to 
change the behavior to fall back on the log4j.properties file in those older 
versions|https://issues.apache.org/jira/browse/ACCUMULO-2349?focusedCommentId=13899776&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13899776].

> Accumulo should give some notification if there is no *_logger.xml file
> -----------------------------------------------------------------------
>
>                 Key: ACCUMULO-2349
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2349
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: John Vines
>             Fix For: 1.7.0
>
>
> Right now if you're missing general_logger and the appropriate 
> service_logger, it seems accumulo just happily carries on with no logs 
> whatsoever. We should alter it to complain loudly if it's missing them.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to