hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Enis Söztutar <enis....@gmail.com>
Subject Re: Does compatibility between versions also mean binary compatibility?
Date Tue, 09 Apr 2013 03:02:51 GMT
I generally agree that we are not at the point of keeping binary or even
source compatibility of Phoenix's use of RegionScanner's etc. In order to
be very flexible, we are giving coprocessors too much control.

For normal client-level API's, I am not convinced that we should keep
binary compatibility between major versions. It will tie our hands of doing
some changes between major versions. An example is essential column family.
If you add a method to a public interface, you make it source incompatible.
Instead we should support
 - Binary and wire compat between minor versions
 - Wire compat and rolling restart between major versions. Rolling upgrade


On Mon, Apr 8, 2013 at 5:40 PM, Andrew Purtell <apurtell@apache.org> wrote:

> Yes of course.
> On Sat, Apr 6, 2013 at 1:11 PM, James Taylor <jtaylor@salesforce.com>
> wrote:
> > That seems reasonable to make an exception for coprocessors on binary
> > compatibility. Can this be explicitly documented if it's not already so
> > folks are sure to know that?
> >
> --
> Best regards,
>    - Andy
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message