immediately and delete it!
-Original Message-
From: Mohammad arshad
Sent: 05 October 2016 19:34
To: d...@zookeeper.apache.org; UserZooKeeper
Subject: RE: ZooKeeper clients does not handle new error codes properly
Thanks Michael Han for the information.
It is the same place in my case as well
tober 2016 10:27
> To: user@zookeeper.apache.org
> Cc: DevZooKeeper
> Subject: Re: ZooKeeper clients does not handle new error codes
> properly
>
> did we bump the protocol version when we added the new errors? the
> server could do the conversion when it responds to older clients.
&g
October 2016 10:27
> To: user@zookeeper.apache.org
> Cc: DevZooKeeper
> Subject: Re: ZooKeeper clients does not handle new error codes properly
>
> did we bump the protocol version when we added the new errors? the server
> could do the conversion when it responds to older clients.
>
zookeeper.apache.org
> Cc: DevZooKeeper
> Subject: Re: ZooKeeper clients does not handle new error codes properly
>
> did we bump the protocol version when we added the new errors? the server
> could do the conversion when it responds to older clients.
>
> On Mon, Oct 3, 2016 at
@zookeeper.apache.org
Cc: DevZooKeeper
Subject: Re: ZooKeeper clients does not handle new error codes properly
did we bump the protocol version when we added the new errors? the server could
do the conversion when it responds to older clients.
On Mon, Oct 3, 2016 at 3:05 AM, Flavio Junqueira wrote:
> Hi Ars
did we bump the protocol version when we added the new errors? the server
could do the conversion when it responds to older clients.
On Mon, Oct 3, 2016 at 3:05 AM, Flavio Junqueira wrote:
> Hi Arshad,
>
> It makes sense to me. What if we convert unknown server errors to
> KeeperException.System
Hi Arshad,
It makes sense to me. What if we convert unknown server errors to
KeeperException.SystemErrorException? This is a generic error and it extends
KeeperException.
I don't see it as a big issue to make this change, but others may feel
differently. If we do it, then we will need a releas
