ppkarwasz commented on issue #2791: URL: https://github.com/apache/logging-log4j2/issues/2791#issuecomment-2267168356
> @ppkarwasz > > I note from https://issues.apache.org/jira/browse/LOG4J2-3644 that the `packages` property seems to be straightforward to remove, though [Migrate log4j2 to logback jmeter#5937](https://github.com/apache/jmeter/issues/5937) on the `apache/jmeter` side is still unclear as to the way forward. There is no problem in Apache Hive: I checked that the appropriate annotation processor is configured in the `hive-exec` project and there is a `Log4j2Plugins.dat` file in the JAR. You can safely remove the `packages` configuration attribute. > * I will say that I personally don't know how to fix [Fix handling of `onMatch` and `onMismatch` attributes in the properties configuration format #2791](https://github.com/apache/logging-log4j2/issues/2791) with the `good first issue` tag. I believe that the problem breaks down to a missing null-check: `ComponentBuilder#addAttribute` should **add** an attribute if the value is not `null` and **remove** it if the value is `null`. `null` is never a valid value for an attribute. BTW: All the problems you are having are due to the fact that `TestHplsqlLocal` and `TestHplsqlOffline` are fragile tests. They write something to `System.out` and they make assertions about that. The problem is: other components (like the status logger) might also write to `System.out`. I proposed a solution to this in apache/hive#5381 -- 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
