Open essobedo opened 1 month ago
I still haven't found a solution for this. Here is what I have discovered so far:
log4j2.xml
or logback.xml
to the classpath + corresponding dependencies makes a difference, but the logs causing the spam aren't affectedoadd.*
-> https://github.com/apache/drill/blob/drill-1.21.2/exec/jdbc-all/pom.xml#L35, <bundle dependency='true'>wrap:mvn:org.apache.drill.exec/drill-jdbc-all/${apache-drill-version}$Export-Package=org.apache.drill.jdbc.*;version=${apache-drill-version}&SPI-Provider=java.sql.Driver</bundle>
ch
folder, from drill-jdbc-all-1.21.2.jar
in my local Maven repo workedInterestingly enough, having this in the integration test classes breaks the test
System.setProperty("logback.configurationFile", ".../logback-test.xml");
It appears that the log level used for the camel-drill feature is DEBUG while INFO is expected which fills up the log file