Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAFb6HiL3H5gtWgEuSD3U5gFB58MCUPFd1h1TaFSGCz-waSsTpQ@mail.gmail.com>
References: 
 <CANZa=GsempdX+fUi5iJfuF6kk8YM6hiB6mOoo8G-U46FKNVEKA@mail.gmail.com>
 <369520731.4581185.1425529245583.JavaMail.yahoo@mail.yahoo.com>
 <CAFb6HiL3H5gtWgEuSD3U5gFB58MCUPFd1h1TaFSGCz-waSsTpQ@mail.gmail.com>
From: Andrew Purtell <apurtell@apache.org>
Date: Thu, 5 Mar 2015 09:43:39 -0800
Message-ID: 
 <CA+RK=_AXJn4uL8=sdrCRCE1SXt4VjtEHh4bqcmiS_FtSk=zqHA@mail.gmail.com>
Subject: Re: Client-Server wire compatibility?
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Cc: lars hofhansl <larsh@apache.org>
Content-Type: multipart/alternative; boundary=001a11c3656814957005108e1e07

--001a11c3656814957005108e1e07
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 5, 2015 at 12:10 AM, Matteo Bertozzi <theo.bertozzi@gmail.com>
wrote:

> On Thu, Mar 5, 2015 at 4:20 AM, lars hofhansl <larsh@apache.org> wrote:
>
> > The idea actually was that a new client can never be 100% supported,
> since
> > a user could use it accessing new features that the server does not
> > understand.
>
>
> I think that it is fine if we have exceptions not handled when a client
> tries to ask a new features on an old server.
> but my question was about old operations. e.g. Assuming that you do a
> create table with all the arguments/configuration that the old server was
> able to understand, is it fair to have a 1.1 client that throws an
> exception against a 1.0 server because in the new 1.1 the create logic is
> not compatible?
>

=E2=80=8B=E2=80=8BThat question hinges on why the create logic is not compa=
tible. =E2=80=8BWe have
guidelines that allow us flexibility to break things at clearly defined
points, but that doesn't mean we shouldn't avoid doing so wherever
possible. Why can't create remain wire compatible in this case? Is there a
JIRA?

--001a11c3656814957005108e1e07--