Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com
 designates 209.85.214.169 as permitted sender)
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: 
 <CAOmV22s6mHgeJ5R80ci3fS++rmEdjk2gvLj1KMO4b9GpEbSn-w@mail.gmail.com>
References: 
 <CAOmV22v2bBy7mHopMENqg2LyQoKvgfQKWSF17MRy9y8CYk2ung@mail.gmail.com>
	<CALte62wychtmpeLhVu7__pgY3x_902a8axK=_b-eh=ejH_6A1Q@mail.gmail.com>
	<CAOmV22v7KSnx+wNrExBUSdOBjZ_og9N+-q0p7f8BcJnPDZhtfg@mail.gmail.com>
	<CADcMMgFYLc=R2bmdLh-iK8udqgguOX0N2KLw5JKpWT8Z_j8NFg@mail.gmail.com>
	<CALte62zd2Zus3P0iB_xNJeGGkBEQvHBSr1h-iitqzBRxZ1iy-A@mail.gmail.com>
	<CAOmV22s6mHgeJ5R80ci3fS++rmEdjk2gvLj1KMO4b9GpEbSn-w@mail.gmail.com>
Date: Mon, 13 Feb 2012 17:10:52 -0800
Message-ID: 
 <CADcMMgH2urcSTg1v5XRK6FcX_U_tarGKMzZpo=P_DG-ovL3VnQ@mail.gmail.com>
Subject: Re: HBase wire compatibility
From: Stack <stack@duboce.net>
To: dev@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 13, 2012 at 4:58 PM, Jimmy Xiang <jxiang@cloudera.com> wrote:
> It is a good idea to swat team it or hackathon.
>
>

Little code has been written at hackathons in the past so it would
need to have a bit of a different format.

Or we just divvy up the work (I could do the migration of .META. and
-ROOT- to pb and of zk persistence to pb if wanted).


> We'd like to start with phase 1 at first, then phase 2.
>
> The purpose is to reduce/eliminate the operation interruption. =A0We need=
 to
> start from somewhere.
>

Agree.

Phase 2 seems just as bad as a disruption as phase 1 or am I reading
it wrong; i.e. its another singularity that can't be crossed w/o a
restart of all servers.

I suppose I'm wondering if we think we can nail phase 1 and phase 2
within a single release cycle; then the two singularities are
experienced as one during a single upgrade.

St.Ack