drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krystal (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (DRILL-1315) Allow specifying Zookeeper root znode and cluster-id as JDBC parameters
Date Wed, 06 May 2015 18:12:02 GMT

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

Krystal reopened DRILL-1315:


Looks like this bug is not fixed.  I updated my drill-override.conf to use a non-default znode:
drill.exec: {
  cluster-id: "krys-drillbits",
  zk.connect: "",
  root: "krystaldrill"

I restarted the drillbit then attempted to connect to sqlline using:
/opt/mapr/drill/drill-0.9.0/bin/sqlline --maxWidth=10000 -n admin -p admin -u jdbc:drill:zk=

I got the following error:
No DrillbitEndpoint can be found

Then I removed the zookeeper path from the connection:
/opt/mapr/drill/drill-0.9.0/bin/sqlline --maxWidth=10000 -n admin -p admin -u jdbc:drill:zk=

This time it connected to the drillbit successfully.  However, it was using the default znode
instead of one configured in the drill-override.conf.  The debug shows:
clientPath:/drill/krys-drillbits serverPath:/drill/krys-drillbits finished:false header::
6,12  replyHeader:: 6,81604397887,0  request:: '/drill/krys-drillbits,T  response:: v{'ac857446-8bb7-4972-8f6c-e36a2309bd17},s{81604397645,81604397645,1430928211935,1430928211935,0,9,0,0,0,1,81604397878}

> Allow specifying Zookeeper root znode and cluster-id as JDBC parameters
> -----------------------------------------------------------------------
>                 Key: DRILL-1315
>                 URL: https://issues.apache.org/jira/browse/DRILL-1315
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>    Affects Versions: 0.5.0
>            Reporter: Aditya Kishore
>            Assignee: DrillCommitter
>             Fix For: 0.5.0
> Currently there is no way to specify a different root z-node and cluster-id to the Drill
JDBC driver and it always attempt to connect to the default values (unless there is a {{drill-override.conf}}
with the correct values also included early in the classpath).

This message was sent by Atlassian JIRA

View raw message