Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/926
On the first comment, it sounds like the close is a placeholder, actual
close is to be done after some refactoring? This is fine. Just a bit surprising
to see a log message, but not actual close.
On the second, yes, Drill uses "unit test" to mean a system test run via
JUnit. Can we create a JUnit-based system test that demonstrates the problem
and fix? I'm guessing that we can do the test at the system level to avoid the
difficulty, at present, of writing true unit tests against Drill code.
---
