ppkarwasz commented on issue #213: URL: https://github.com/apache/logging-log4j-transform/issues/213#issuecomment-3153645681
Good catch! :100: It turns out that `rootLogger.appenderRefs` and `logger.<name>.appenderRefs` **were** valid keys in the Log4j 2 properties config format: * They were present in Log4j 2.4.x and 2.5. * They were inadvertently removed in 2.6 along with other keys that represented arrays (like `appenders`, `loggers`, etc.). * Some of those keys were later restored in [LOG4J2-1402](https://issues.apache.org/jira/browse/LOG4J2-1402). * But `appenderRefs` never made it back. * Since version 2.6 all the properties that list keys in an array are no longer needed. This highlights a core issue I have with the `v2:properties` format: some keys are hardcoded, and their structure follows special rules that aren't easily inferred or translated: ```properties property script customLevel appender appender.filter rootLogger rootLogger.appenderRef rootLogger.filter logger logger.appenderRef logger.filter ``` These top-level constructs are treated specially, while deeper structures (e.g., within appenders or layouts) are consistent and predictable. Do you think I should also support `properties` and `customLevels` keys, even though they never actually existed, since some users might reasonably assume they're valid? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
