linghengqian commented on issue #2791: URL: https://github.com/apache/logging-log4j2/issues/2791#issuecomment-2266347013
@ppkarwasz - Late reply, because I need to wait for verification on `apache/hive`'s CI side. `apache/hive`'s CI resources are too tight, and `apache/hive`'s jenkins node limits each contributor to 5 hours between 2 consecutive CIs. To be honest, https://github.com/apache/hive/pull/5375 is the first PR I opened on apache/hive's side, and I know almost nothing about `apache/hive`'s logging design. - I updated https://github.com/apache/hive/pull/5375 not long ago, I removed the `packages`, `appenders`, `loggers` nodes of `/hive/data/conf/hive-log4j2.properties`, and changed `logger.CBORuleLogger.filter.marker.onMisMatch` to `logger.CBORuleLogger.filter.marker.onMismatch`. `apache/hive`'s CI is now back on apache/logging-log4j2:2.23.0. I'm assuming this is a reasonable way forward to not break compatibility with future versions of log4j2. I'm assuming the changes are in line with what's documented in https://github.com/apache/pulsar/pull/22327 , https://logging.apache.org/log4j/2.x/manual/configuration.html , and https://logging.apache.org/log4j/2.x/manual/plugins.html . I note from https://issues.apache.org/jira/browse/LOG4J2-3644 that the `packages` property seems to be straightforward to remove, though https://github.com/apache/jmeter/issues/5937 on the `apache/jmeter` side is still unclear as to the way forward. - On the `apache/hive` side, I noticed a new issue when bump from `apache/logging-log4j2:2.23.0` to `apache/logging-log4j2:2.23.1`, the `status = INFO` defined in `hive-log4j2.properties` is no longer valid, and Log4j2 internal logs at `TRACE` and `DEBUG` levels will be printed starting from `apache/logging-log4j2:2.23.1`. Since the current issue is bound to https://issues.apache.org/jira/browse/LOG4J2-2931 , I opened #2794 to avoid ambiguity. - I will say that I personally don't know how to fix #2791 with the `good first issue` tag. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
