You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Parth Chandra (JIRA)" <ji...@apache.org> on 2015/04/08 01:47:14 UTC

[jira] [Updated] (DRILL-1773) Issues when using JAVA code thourgh Drill JDBC driver

     [ https://issues.apache.org/jira/browse/DRILL-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Parth Chandra updated DRILL-1773:
---------------------------------
    Fix Version/s:     (was: 0.9.0)
                   1.0.0

> Issues when using JAVA code thourgh Drill JDBC driver
> -----------------------------------------------------
>
>                 Key: DRILL-1773
>                 URL: https://issues.apache.org/jira/browse/DRILL-1773
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>    Affects Versions: 0.6.0, 0.7.0
>         Environment: Tested on 0.6R3
>            Reporter: Hao Zhu
>            Assignee: Daniel Barclay (Drill)
>             Fix For: 1.0.0
>
>         Attachments: DrillHandler.patch, DrillJdbcExample.java
>
>
> 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:
> {code}
> 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
> {code}
> 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.
> {code}
> 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$ 
> {code}
> ========
> The DrillJdbcExample.java is attached.
> Command to run:
> {code}
> javac DrillJdbcExample.java
> java DrillJdbcExample
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)