[
https://issues.apache.org/jira/browse/LOG4J2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488286#comment-17488286
]
Matt Sicker commented on LOG4J2-3394:
-------------------------------------
So one of the hard parts to solve here is a combination of two factors:
# Supporting a sort of compound value here with string substitution is
difficult as string substitution applies to plugin attributes and values down
the tree, but if we apply string substitution while pre-processing the
properties, then substitution would be applied twice.
# Introducing a new plugin or syntax for setting multiple values in a single
attribute is a bit of a hack if it's only important for properties files.
Now this idea isn't the cleanest, either, but what if we had a separate
properties substitution syntax here? Like #\{property} or something like that.
We could adapt some ideas on lazy-vs-eager variable substitution from Spring's
expression language where $ and # mean different things.
> 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)
