I failed to mark 246 as an incompatible change in JIRA/releasenotes:
KeeperException.Code was changed from an interface to an enum, the old
camel case Code fields (Ok, NoNode, etc...) were deprecated and replaced
by upper case versions (OK, NONODE, etc...). Similar change in the C
I thought I verified this worked with legacy code (deprecated still
worked), but I guess not. I'll fix this in the code to make it b/w
compat and also update the release notes -- I'll respin a new release
Thanks for the heads up Stu!
Stu Hood wrote:
This candidate passes all of our unit tests.
Has the disk or wire format changed from 3.0.1 to 3.1.0?
There was one difference that prevented our code base from building
immediately: the deprecated integers in KeeperException.Code were not working
in switch statements anymore:
[javac] Compiling 91 source files to deploy/classes
[javac] src/java/mercury/ring/KeySpace.java:796: constant expression required
[javac] case Code.Ok:
[javac] src/java/mercury/ring/KeySpace.java:800: constant expression required
[javac] case Code.NoNode:
[javac] src/java/mercury/ring/KeySpace.java:803: constant expression required
[javac] case Code.SessionExpired:
[javac] src/java/mercury/ring/KeySpace.java:804: constant expression required
[javac] case Code.ConnectionLoss:
From: "Patrick Hunt" <ph...@apache.org>
Sent: Tuesday, February 3, 2009 8:37pm
To: "firstname.lastname@example.org" <email@example.com>
Subject: [VOTE] Release ZooKeeper 3.1.0 (candidate 0)
I've created a candidate build for ZooKeeper 3.1.0. Over 65 JIRAs are
addressed in this release, with major new features for Quota, JMX, and
Bookkeeper (transactional log store) to name a few. Full details in the
*** Please download, test and VOTE before the
*** vote closes EOD on Friday, February 6.***
Should we release this?