Drill Developer Day

Hi All, Please find the attached link to register for the Drill Developer Day event. https://www.eventbrite.com/e/apache-drill-developer-day-tickets-52121673328 Thank you, Jyothsna

Re: logging in test cases produces two outputs

Hi JC, Your code looks fine. I usually start with the default log level (ERROR), then turn on DEBUG for specific modules, as you do. I then see my INFO or DEBUG messages. My code looks like yours, so I'm not sure why you are seeing two messages. Perhaps you are logging ERROR level messages?

logging in test cases produces two outputs

I'm using the LogFixture LogFixtureBuilder logBuilder = LogFixture.builder() // Log to the console for debugging convenience .toConsole().logger("org.apache.drill.exec.store.msgpack", Level.DEBUG); try (LogFixture logs = logBuilder.build()) { Basice logback.xml file is However when I

[GitHub] bitblender commented on a change in pull request #1467: DRILL-5671: Set secure ACLs (Access Control List) for Drill ZK nodes in a secure cluster

bitblender commented on a change in pull request #1467: DRILL-5671: Set secure ACLs (Access Control List) for Drill ZK nodes in a secure cluster URL: https://github.com/apache/drill/pull/1467#discussion_r230560459 ## File path:

[GitHub] weijietong commented on issue #1504: DRILL-6792: Find the right probe side fragment wrapper & fix DrillBuf…

weijietong commented on issue #1504: DRILL-6792: Find the right probe side fragment wrapper & fix DrillBuf… URL: https://github.com/apache/drill/pull/1504#issuecomment-435592972 @sohami please give a review. This commit contains a performance improvement to make the foreman node to