drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Barclay (Drill) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-3015) Can't connect to Squirrel using JDBC
Date Mon, 11 May 2015 17:53:01 GMT

    [ https://issues.apache.org/jira/browse/DRILL-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538274#comment-14538274

Daniel Barclay (Drill) commented on DRILL-3015:

> Any updates on this issue? Appreciate your response.

You'll have to be patient; we're in the middle of getting the 1.0 release out.

Have you been able to connect using SQLLine?  (If so, which JDBC URL(s) worked?)

Can you get any more of an error message than "Cannot open SQL connection" out of Squirrel
(so we can see what error Squirrel is getting from Drill's JDBC driver)?  Does Squirrel have
a verbose mode, or logging?

Related to that, I happen to be working on DRILL-3020.  Once that's in, Squirrel's  "Cannot
open SQL connection" message might include more text, which might indicate more about the


> Can't connect to Squirrel using JDBC
> ------------------------------------
>                 Key: DRILL-3015
>                 URL: https://issues.apache.org/jira/browse/DRILL-3015
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>    Affects Versions: 0.9.0
>            Reporter: Murtaza
>            Assignee: Daniel Barclay (Drill)
>            Priority: Blocker
> Please suggest me what jdbc url to use with Squirrel. I have installed Apache Drill 0.9
on standalone macbook. I had given all types of jdbc url like below
> jdbc:drill:zk=;schema=dfs
> jdbc:drill:zk=;schema=dfs
> jdbc:drill:zk=KWTLT01407.local:5181/drill/drillbits1;schema=dfs
> jdbc:drill:zk=KWTLT01407.local:2181/drill/drillbits1;schema=dfs
> All is giving me error in Squirrel stating "Cannot open SQL connection".
> Please suggest me how to use JDBC to connect to Apache Drill installed on standalone

This message was sent by Atlassian JIRA

View raw message