, please notify
the sender by
phone or email immediately and delete it!
-Original Message-
From: Patrick Hunt [mailto:ph...@apache.org]
Sent: 25 May 2016 23:19
To: DevZooKeeper
Subject: Re: How to extend ZooKeeper data structure without breaking the
backward compatibility
Hm. What you&#x
onfidential information from
> HUAWEI, which is intended only for the person or entity whose address is
> listed above. Any use of the information contained herein in any way
> (including, but not limited to, total or partial disclosure, reproduction,
> or dissemination) by persons othe
e
> intended
> recipient(s) is prohibited. If you receive this e-mail in error, please
> notify the sender by
> phone or email immediately and delete it!
>
>
> -Original Message-
> From: Mohammad arshad
> Sent: 24 May 2016 11:12
> To: DevZooKeeper
> Subject: RE: How
!
-Original Message-
From: Mohammad arshad
Sent: 24 May 2016 11:12
To: DevZooKeeper
Subject: RE: How to extend ZooKeeper data structure without breaking the
backward compatibility
Thanks Patrick and Falvio
I also was more inclined towards the option 3 but it does not solve the problem.
It
03:58
To: DevZooKeeper
Subject: Re: How to extend ZooKeeper data structure without breaking the
backward compatibility
I thought we added the version to the file header for exactly this case.
Allowing the server to differentiate in case we need to upgrade the on-disk
format. Option 3 seems the
t; total or partial
> > disclosure, reproduction, or dissemination) by persons other than the
> > intended
> > recipient(s) is prohibited. If you receive this e-mail in error, please
> > notify the sender by
> > phone or email immediately and delete it!
> >
> >
>
> notify the sender by
> phone or email immediately and delete it!
>
>
> -Original Message-
> From: Flavio Junqueira [mailto:f...@apache.org]
> Sent: 11 May 2016 18:18
> To: u...@zookeeper.apache.org
> Cc: dev@zookeeper.apache.org
> Subject: Re: How to extend Zoo
To: u...@zookeeper.apache.org
Cc: dev@zookeeper.apache.org
Subject: Re: How to extend ZooKeeper data structure without breaking the
backward compatibility
In this case, I guess we have to check the protocol version and depending on
the version deserialize differently.
-Flavio
> On 11 May 2
and delete it!
>
> -Original Message-
> From: Flavio Junqueira [mailto:f...@apache.org]
> Sent: 11 May 2016 16:02
> To: u...@zookeeper.apache.org
> Cc: Zookeeper
> Subject: Re: How to extend ZooKeeper data structure without breaking the
> backward compatibility
>
&g
May 2016 16:02
To: u...@zookeeper.apache.org
Cc: Zookeeper
Subject: Re: How to extend ZooKeeper data structure without breaking the
backward compatibility
In the past, we simply created two versions of the data structure:
class CreateTxnV0 {
ustring path;
buffer data
In the past, we simply created two versions of the data structure:
class CreateTxnV0 {
ustring path;
buffer data;
vector acl;
boolean ephemeral;
}
class CreateTxn {
ustring path;
buffer data;
vector acl;
boolean ephemeral;
11 matches
Mail list logo
