Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 31EAC17ACB for ; Fri, 24 Oct 2014 17:02:25 +0000 (UTC) Received: (qmail 70040 invoked by uid 500); 24 Oct 2014 17:02:25 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 69998 invoked by uid 500); 24 Oct 2014 17:02:25 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 69987 invoked by uid 99); 24 Oct 2014 17:02:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Oct 2014 17:02:24 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.220.41] (HELO mail-pa0-f41.google.com) (209.85.220.41) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Oct 2014 17:01:58 +0000 Received: by mail-pa0-f41.google.com with SMTP id rd3so1487225pab.0 for ; Fri, 24 Oct 2014 10:00:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:content-type; bh=lG8cclKY3GJ4SnUEfPg9XXUK2BAvc4eNJRRtPWFLQQA=; b=UZXTjLuBIPYdghTk99mZCO3Krc4bxth3kyCmymASIELWKzifpkB08dn57jxtc/Trav pooZ3Zzls85S7zQWHeLb1ov4fybcBmWs5EBWFTTojsNiKl9l4xczo9T5ECycqZDCIuJA 30+hIk8gIfu4NaH2ua5iDm5NrUDFlzekXRC1z0zMswiSjaafgQKMBfneK73qqMWyzujx MmrztiEBYj6xg6OR+OwhZkM1XDtcVmyC9GChcV/koX0QqOMelYs9pAKGs7Sug349FbWI 1FaBRjjVjLXNWN81BPngwnayWpaYXKyWgHh91l2vBj9BDIcesD5K5ePx95YljnnDldIh E1Ig== X-Gm-Message-State: ALoCoQmc1dOhxRQHPZ7gVTkM3R03ZOgVTdTTxe44tkG6UDq8FWDUO//JhAqUQalDCsrHq9OqS5sP X-Received: by 10.70.126.40 with SMTP id mv8mr5714463pdb.109.1414170026045; Fri, 24 Oct 2014 10:00:26 -0700 (PDT) Received: from Jordans-MacBook-Pro.local ([190.141.38.38]) by mx.google.com with ESMTPSA id ir7sm4323558pbc.15.2014.10.24.10.00.22 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Fri, 24 Oct 2014 10:00:23 -0700 (PDT) Date: Fri, 24 Oct 2014 12:00:21 -0500 From: Jordan Zimmerman To: Mike Drob Cc: dev@curator.apache.org, Cameron McKenzie Message-ID: In-Reply-To: References: Subject: Re: ZooKeeper 3.5.0 is coming X-Mailer: Airmail (249) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="544a85a5_1190cde7_3938" X-Virus-Checked: Checked by ClamAV on apache.org --544a85a5_1190cde7_3938 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline When 3.4.5 came out with the transaction APIs I just documented that vers= ion X.X.X (I forget which) was the last version of Curator that would sup= port 3.3.x and below. We could do the same for this. -JZ On October 24, 2014 at 11:58:48 AM, Mike Drob (madrob=40cloudera.com) wro= te: I would strongly prefer to have one version, even if it means that we nee= d to do some reflection hacking under the hood. I think it greatly simpli= fies the narrative for users both when starting out and when upgrading. On =46ri, Oct 24, 2014 at 11:50 AM, Jordan Zimmerman wrote: I haven=E2=80=99t had time. The upcoming ZooKeeper meetup should give det= ails on when to expect 3.5.0. One thing we might need to do is have two v= ersions of Curator for a while as not everyone will move to 3.5.0 immedia= tely. -Jordan On October 24, 2014 at 12:03:41 AM, Cameron McKenzie (mckenzie.cam=40gmai= l.com) wrote: Has anyone had any further thoughts about ZK 3.5 and dynamic cluster reco= nfiguration=3F I had a look into the EnsembleProvider interface, but I don't think that = it will work because it is used to create the connection to ZooKeeper, an= d from my (limited) understanding of the way that cluster configuration w= orks in ZK 3.5, you need a connection to ZK before you can work out all o= f the nodes in the cluster. So, there is a bit of a chicken and egg probl= em. cheers Cam On =46ri, Aug 8, 2014 at 2:20 AM, Jordan Zimmerman wrote: We could use a label. However, I have version 3.0.0 set for ZK 3.5.x comp= atibility so we can just use that. -JZ =46rom:=C2=A0Mike Drob Reply:=C2=A0dev=40curator.apache.org > Date:=C2=A0August 7, 2014 at 10:28:16 AM To:=C2=A0dev=40curator.apache.org > Cc:=C2=A0Cameron McKenzie > Subject:=C2=A0 Re: ZooKeeper 3.5.0 is coming I saw that they added the ability to remove watches, so that could be a viable approach for CURATOR-14=3F Are we using a JIRA label to group the issues and make them easily findab= le=3F Mike On Thu, Aug 7, 2014 at 9:54 AM, Jordan Zimmerman wrote: > I think we should list all the changes that we need to do and get Jira=E2= =80=99s > written for them (targeted for version 3.0.0) and then we can divide up= the > work. > > -JZ > > > =46rom: Cameron McKenzie > Reply: dev=40curator.apache.org > > Date: August 7, 2014 at 12:45:21 AM > To: dev=40curator.apache.org > > Subject: Re: ZooKeeper 3.5.0 is coming > > I'm happy to start looking into this in a bit more detail unless someon= e > else has their heart set on it. > cheers > Cam > --544a85a5_1190cde7_3938--