[
https://issues.apache.org/jira/browse/LOG4J2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488630#comment-17488630
]
Ralph Goers commented on LOG4J2-3394:
-------------------------------------
The original request was to support the compound attribute to make it more
compatible with what is being done with log4j1 properties configurations .The
XML configuration for Log4j 1 does not support this.
We are implementing this for the sole purpose of making the transition of
Hadoop scripts easier, although we've pointed out that the Hadoop scripts could
have handled this with no changes to Log4j2.
Modifying the LoggerConfig means it will apply to all formats. I do not want
that. The XML, Yaml, and JSON syntaxes are fine just the way they are.
introducing the notion of
{code:java}
<Root config="INFO, Console, File"/>
{code}
Is not at all appealing to me, especially since it loses functionality. to be
complete it would have to be something like:
{code:java}
<Root config="INFO, MarkerFilter(marker=FLOW, onMatch=ACCEPT,
onMismatch=NEUTRAL), {Console, DEBUG}, File, {File2, DEBUG, RegexFilter
regex='.* test .*' onMatch=ACCEPT onMismatch=DENY"/>
{code}
which is completely ridiculous when you are dealing with a configuration format
that is already well structured. Plus, parsing that string would be
error-prone. To top it off, the equivalent syntax in JSON would be
{code:java}
"Root": {"level": "debug", "AppenderRef": [{"ref": "Console"}, {"ref":
"File"}]}{code}
which I personally find to be much more readable and far less error prone as
there is absolutely no ambiguity.
If you want to do that however, you are free to create your own
ConfigurationFactory.
> The 'rootLogger=${sys:root.logger:-INFO,console}' does not work
> ---------------------------------------------------------------
>
> Key: LOG4J2-3394
> URL: https://issues.apache.org/jira/browse/LOG4J2-3394
> Project: Log4j 2
> Issue Type: Bug
> Components: Configuration
> Reporter: Duo Zhang
> Priority: Major
> Attachments: log4j2.err, log4j2.properties
>
>
> Tried the new feature introduced in LOG4J2-3341 in hbase.
> https://github.com/apache/hbase/pull/4096
> I built a tarball and try to start a standalone hbase instance locally, but
> log4j2 failed to load the system properties of rootLogger.
> Will upload the config and error output.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
