[
https://issues.apache.org/jira/browse/LOG4J2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488416#comment-17488416
]
Volkan Yazici commented on LOG4J2-3394:
---------------------------------------
I think _"[~ckozak] and [~vy] have vetoed the fix above"_ needs some
explanation. We simply didn't approve the way interpolation was implemented in
the fix and that rendered the fix unusable. I see the point of the use case and
want to make it work using Log4j. Though rather than implementing this as a
Log4j feature, I am in favor of, if necessary, making Log4j extensible enough
such that this feature could simply be implemented using plugins by the user.
For instance, can we simply support the requested feature via a custom
{{HadoopPropertiesConfigurationFactory}} which is a slight derivation of our
stock {{PropertiesConfigurationFactory}}? Or the aforementioned
{{CompoundProperty}}?
> 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)
