[
https://issues.apache.org/jira/browse/ACCUMULO-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899776#comment-13899776
]
Christopher Tubbs commented on ACCUMULO-2349:
---------------------------------------------
I'd rather we just get rid of this mechanism entirely, and rely on the
log4j.properties (or alternate log4j.xml) or whatever logging configuration is
appropriate for their logging framework. These are very non-standard and users
shouldn't really be burdened by them. We shouldn't have custom code to deal
with these.
In the interim, a good workaround is to fall back to initializing log4j
normally (with the usual log4j.properties or log4j.xml files, and complain in
whatever default way log4j likes to complain if those files don't exist). I
think that fallback is better than complaining about missing custom
configuration files, especially if we plan for that custom stuff to go away
(and I think we should plan for that case).
> 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)
