Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.6.0, 0.7.0
-
None
-
Tested on 0.6R3
Description
When executing attached simple JAVA code through Drill JDBC driver(0..6 R3), the query got executed and returned the correct result, however there are 2 issues:
1. It keeps printing DEBUG information.
Is it default behavior or is there any way to disable DEBUG?
eg:
13:30:44.702 [Client-1] DEBUG i.n.u.i.JavassistTypeParameterMatcherGenerator - Generated: io.netty.util.internal.__matchers__.io.netty.buffer.ByteBufMatcher
13:30:44.706 [Client-1] DEBUG i.n.u.i.JavassistTypeParameterMatcherGenerator - Generated: io.netty.util.internal.__matchers__.org.apache.drill.exec.rpc.OutboundRpcMessageMatcher
13:30:44.708 [Client-1] DEBUG i.n.u.i.JavassistTypeParameterMatcherGenerator - Generated: io.netty.util.internal.__matchers__.org.apache.drill.exec.rpc.InboundRpcMessageMatcher
13:30:44.717 [Client-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.maxCapacity.default: 262144
2. After the query finished, it seems not close the connection and did not return to shell prompt.
I have to manually issue "ctrl-C" to stop it.
13:31:11.239 [main-SendThread(xx.xx.xx.xx:5181)] DEBUG org.apache.zookeeper.ClientCnxn - Got ping response for sessionid: 0x1497d1d0d040839 after 0ms 13:31:24.573 [main-SendThread(xx.xx.xx.xx:5181)] DEBUG org.apache.zookeeper.ClientCnxn - Got ping response for sessionid: 0x1497d1d0d040839 after 1ms 13:31:37.906 [main-SendThread(xx.xx.xx.xx:5181)] DEBUG org.apache.zookeeper.ClientCnxn - Got ping response for sessionid: 0x1497d1d0d040839 after 0ms ^CAdministrators-MacBook-Pro-40:xxx$
========
The DrillJdbcExample.java is attached.
Command to run:
javac DrillJdbcExample.java java DrillJdbcExample
Attachments
Attachments
Issue Links
- is superceded by
-
DRILL-3741 Document logging configuration for JDBC-all
- Open