Thanks Paul, forgot about that. I'll migrate all the tests off of
System.out.print and onto LogFixture, I don't think its worth it to create a
TestLogger.out since we should all be using loggers anyway. I'll also add a
checkstyle check that will cause the build to fail of System.out.print is
LogFixture? As illustrated in ExampleTest?
This fixture lets you turn on all or selected loggers for the duration of a
single test. I used it all the time when debugging. Works great.
It works when turning loggers on when the default is that they are off. For
whatever reason, I could not get it
Hi All,
I was wondering if there was a magical way to enable the Slf4j loggers for unit
tests without adding a logback-test.xml file into src/test/resources for a
submodule in the project? If not, would there by any issues with adding a
default logback-test.xml file that has logging disabled
I believe Drill web site and documentation is generated automatically from
the gh_pages. Moving this is probably not advisable.
On Tue, May 22, 2018 at 3:14 PM, Boaz Ben-Zvi wrote:
> Done – all three were deleted, using github (thanks @Vlad Rozov).
>
> There is also an
Sorabh Hamirwasia created DRILL-6445:
Summary: Fix existing test cases in TestScripts.java and add new
test case for DRILLBIT_CONTEXT variable
Key: DRILL-6445
URL:
Boaz Ben-Zvi created DRILL-6444:
---
Summary: Hash Join: Avoid partitioning when memory is sufficient
Key: DRILL-6444
URL: https://issues.apache.org/jira/browse/DRILL-6444
Project: Apache Drill