Return-Path: 
 <issues-return-264-apmail-drill-issues-archive=drill.apache.org@drill.incubator.apache.org>
X-Original-To: apmail-drill-issues-archive@minotaur.apache.org
Delivered-To: apmail-drill-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 30A2C10AAB
	for <apmail-drill-issues-archive@minotaur.apache.org>;
 Thu, 29 May 2014 01:36:26 +0000 (UTC)
Received: (qmail 73695 invoked by uid 500); 29 May 2014 01:36:26 -0000
Delivered-To: apmail-drill-issues-archive@drill.apache.org
Received: (qmail 73671 invoked by uid 500); 29 May 2014 01:36:26 -0000
Mailing-List: contact issues-help@drill.incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@drill.incubator.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@drill.incubator.apache.org>
List-Post: <mailto:issues@drill.incubator.apache.org>
List-Id: <issues.drill.incubator.apache.org>
Reply-To: dev@drill.incubator.apache.org
Delivered-To: mailing list issues@drill.incubator.apache.org
Received: (qmail 73662 invoked by uid 99); 29 May 2014 01:36:26 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 01:36:26 +0000
X-ASF-Spam-Status: No, hits=-2000.7 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3)
    by apache.org (qpsmtpd/0.29) with SMTP; Thu, 29 May 2014 01:36:26 +0000
Received: (qmail 72971 invoked by uid 99); 29 May 2014 01:36:01 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 01:36:01 +0000
Date: Thu, 29 May 2014 01:36:01 +0000 (UTC)
From: "Parth Chandra (JIRA)" <jira@apache.org>
To: issues@drill.incubator.apache.org
Message-ID: <JIRA.12715305.1400536169488.36196.1401327361443@arcas>
In-Reply-To: <JIRA.12715305.1400536169488@arcas>
References: <JIRA.12715305.1400536169488@arcas>
Subject: [jira] [Commented] (DRILL-780) ZooKeeper connection to support
 configurable cluster id
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Parth Chandra commented on DRILL-780:
-------------------------------------

To support this change we are changing the connect string format.  Note that the cluster id is not sufficient, the client needs to accept the path to the drill root in zookeeper as well. This path and cluster id will now be appended to the end of the connect string.
In addition, the jdbc:drill prefix seems odd and will be removed.

Final canonical form of the connect string:

zk=zk1:port[,,zk2:p2,...][/<path_to_drill_root>/<cluster_id>]"
examples:
        zk=localhost:2181
        zk=localhost:2181/drill/drillbits1
        zk=localhost:2181,zk2:2181/drill/drillbits1

The connect string to connect directly to a drillbit :
local=host:port
example:
        local=127.0.0.1:31010



> ZooKeeper connection to support configurable cluster id
> -------------------------------------------------------
>
>                 Key: DRILL-780
>                 URL: https://issues.apache.org/jira/browse/DRILL-780
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: George Chow
>
> The cluster-id will have to be configurable and part of the connect string. Default is drillbit1. If the connection type is local, I will ignore the cluster-id if provided.
>   The connect string URL will be like :
> jdbc:drill:[cluster-id=<clusterid>;]zk=zk1:5181,zk2:5181,zk3:5181  



--
This message was sent by Atlassian JIRA
(v6.2#6252)