hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Rodionov <vladrodio...@gmail.com>
Subject Re: Could you please stop breaking API compatibility?
Date Tue, 30 Sep 2014 04:22:59 GMT
Yes, sure

I just forgot that master is 2.0.

-Vladimir Rodionov

On Mon, Sep 29, 2014 at 9:09 PM, Anoop John <anoop.hbase@gmail.com> wrote:

> This API was deprecated since 0.96.  HBase 2.0 is the 3rd major version
> after 0.96 and we should remove the deprecated items at some point of time
> right?  I believe 2.0 is the place we must do a clean up of removing
> deprecated items.  Pls correct if saying wrong.
>
> -Anoop-
>
> On Tue, Sep 30, 2014 at 1:41 AM, Enis Söztutar <enis.soz@gmail.com> wrote:
>
> > We are not changing APIs for the sake of breaking them. We are trying to
> > gradually move to better and more performant APIs. As others have said
> > there is now some work going on in the branch-1 branch to stabilize the
> API
> > layer for 1.x series of releases. Master branch is scheduled for 2.x
> series
> > and accordingly it may contain breaking changes.
> >
> > branch-1 contains a lot of deprecated APIs that are scheduled to be
> removed
> > in 2.x series. Please take a look at the new replacement API in branch-1
> to
> > see whether they make sense or not.
> >
> > Enis
> >
> > On Mon, Sep 29, 2014 at 11:28 AM, Stack <stack@duboce.net> wrote:
> >
> > > Vladimir:
> > >
> > > You are referring to a change in master branch?  Master branch will
> > become
> > > Apache HBase 2.0.  There will be incompatible differences between 1.0
> and
> > > 2.0.  As the lads have said, doc., coming on our guarantees in
> versioning
> > > regard.  Sorry you got caught in the middle.
> > >
> > > St.Ack
> > >
> > > On Mon, Sep 29, 2014 at 10:39 AM, Andrew Purtell <apurtell@apache.org>
> > > wrote:
> > >
> > > > When 1.0 is released we will employ semantic versioning and will
> > > > publicly release a document detailing compatibility guarantees you
> can
> > > > expect between major, minor, and patch releases. Until 1.0 is
> > > > released, we reserve the right to make breaking API changes in
> > > > preparation for 1.0. Note that breaking Java API changes are
> different
> > > > from wire compatibility issues. We do not expect to affect wire
> > > > compatibility.
> > > >
> > > >
> > > >
> > > > On Mon, Sep 29, 2014 at 10:32 AM, Vladimir Rodionov
> > > > <vladrodionov@gmail.com> wrote:
> > > > > I just updated master and found that
> > > > >
> > > > > Put.getFamilyMap went missing (apparently has been renamed to
> > > > > getFamilyCellMap)
> > > > >
> > > > > -Vladimir
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > >
> > > >    - Andy
> > > >
> > > > Problems worthy of attack prove their worth by hitting back. - Piet
> > > > Hein (via Tom White)
> > > >
> > >
> >
>

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