Hi Taewoo, The new argument to set is -Dlog4j.configurationFile and you need to provide a log4j2 compatible configuration file. It is more or less similar to logging.properties. You can check [1] for more details about the configuration. We already have a configuration file that you can use and modify under asterix-app/src/test/resources/log4j2-test.xml. Changing the configuration there should reflect the changes on the tests. One thing to note is that log4j2 log levels are different than java logging. You can check [2] for the mapping between the old and the new levels.
Cheers, Murtadha [1] https://logging.apache.org/log4j/2.0/manual/configuration.html [2] https://logging.apache.org/log4j/2.0/log4j-jul/index.html On 12/20/2017, 10:38 AM, "Taewoo Kim" <[email protected]> wrote: Hello All, Not long time ago, for each test suite (e.g., OptimizerTest), we can provide a custom log level property file (logging.properties) as a VM option (e.g., -Djava.util.logging.config.file=/.../asterixdb/asterixdb/asterix-app/src/test/resources/logging.properties) and customize logging level for each phase (Hyracks, Algebricks, and so on). For example, if I set "org.apache.hyracks.algebricks.level = FINE", then only logging level for Algebricks is changed to FINE. It seems that this method doesn't work anymore. Could somebody tell me how we could set a custom logging level for each phase? Thanks! Best, Taewoo
