You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Vladimir Rodionov <vl...@gmail.com> on 2014/09/29 19:32:04 UTC
Could you please stop breaking API compatibility?
I just updated master and found that
Put.getFamilyMap went missing (apparently has been renamed to
getFamilyCellMap)
-Vladimir
Re: Could you please stop breaking API compatibility?
Posted by lars hofhansl <la...@apache.org>.
We will publish an official compatibility statement for comment soon. We discussed a proposal at the last PMC meeting.
-- Lars
________________________________
From: Andrew Purtell <ap...@apache.org>
To: "dev@hbase.apache.org" <de...@hbase.apache.org>
Sent: Monday, September 29, 2014 10:39 AM
Subject: Re: Could you please stop breaking API compatibility?
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
<vl...@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)
Re: Could you please stop breaking API compatibility?
Posted by Vladimir Rodionov <vl...@gmail.com>.
Yes, sure
I just forgot that master is 2.0.
-Vladimir Rodionov
On Mon, Sep 29, 2014 at 9:09 PM, Anoop John <an...@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 <en...@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 <st...@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 <ap...@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
> > > > <vl...@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)
> > > >
> > >
> >
>
Re: Could you please stop breaking API compatibility?
Posted by Anoop John <an...@gmail.com>.
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 <en...@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 <st...@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 <ap...@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
> > > <vl...@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)
> > >
> >
>
Re: Could you please stop breaking API compatibility?
Posted by Enis Söztutar <en...@gmail.com>.
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 <st...@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 <ap...@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
> > <vl...@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)
> >
>
Re: Could you please stop breaking API compatibility?
Posted by Stack <st...@duboce.net>.
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 <ap...@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
> <vl...@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)
>
Re: Could you please stop breaking API compatibility?
Posted by Andrew Purtell <ap...@apache.org>.
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
<vl...@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)