You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Jim Kellerman <ji...@powerset.com> on 2008/08/22 00:45:14 UTC
[Announcement] hbase-0.18.0 is now feature frozen
Since hadoop-0.18 is now available, hbase-0.18.0 is now feature frozen.
The only changes that will be accepted until hbase-0.18.0 is released are blocker level bug fixes.
I will be moving Jiras for feature requests from 0.18.0 to 0.19.0
---
Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
Re: [Announcement] hbase-0.18.0 is now feature frozen
Posted by Billy Pearson <sa...@pearsonwholesale.com>.
They deiced to keep release numbers with the releases of hadoop
sense hadoop 0.18 is out we should be pushing a version out that uses 0.18
This just means we will be rolling version and releasing more often to keep
up with hadoop.
But that's fine with me I like release often lets people use new features
with out
having to play with trunk and risk losing data up major changes.
Billy
"stack" <st...@duboce.net> wrote in message
news:7c962aed0808211908u75937e14nc8fe05ad15b888ca@mail.gmail.com...
> And if you mean 0.3.0 is feature-frozen, as Rong-en asks, shouldn't we
> discuss first before calling it feature-complete?
>
> St.Ack
>
>
> On Thu, Aug 21, 2008 at 6:18 PM, Rong-en Fan
> <gr...@gmail.com> wrote:
>
>> Do you mean HBase-0.3.0??
>>
>> On Fri, Aug 22, 2008 at 6:45 AM, Jim Kellerman
>> <ji...@powerset.com> wrote:
>> > Since hadoop-0.18 is now available, hbase-0.18.0 is now feature frozen.
>> >
>> > The only changes that will be accepted until hbase-0.18.0 is released
>> > are
>> blocker level bug fixes.
>> >
>> > I will be moving Jiras for feature requests from 0.18.0 to 0.19.0
>> >
>> > ---
>> > Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
>> >
>> >
>>
>
RE: [Announcement] hbase-0.18.0 is now feature frozen
Posted by Jim Kellerman <ji...@powerset.com>.
Most of the changes to Hadoop don't really affect HBase except for binary compatibility (Hadoop changes an RPC interface, etc). In this case, we need to have a release that works with the new version of Hadoop, but usually we aren't using new features. (HDFS appends are the big exception to this)
We tried (and mostly succeeded) in including everything that would break compatibility in 0.2.0 (which is why it took so long to get out). I'm hopeful that future releases will be less disruptive than 0.2 and will allow us to move forward more briskly.
Finally, we are building a community (although it is not as big as Hadoop's) and I and the other committers really appreciate contributions that have come from people who use HBase and want to make it better. Thank you all!
---
Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> -----Original Message-----
> From: Jean-Daniel Cryans [mailto:jdcryans@gmail.com]
> Sent: Friday, August 22, 2008 9:48 AM
> To: hbase-user@hadoop.apache.org
> Subject: Re: [Announcement] hbase-0.18.0 is now feature frozen
>
> Well we still have to support every new Hadoop release but this will mean
> fewer features in each release. In a way it's a good thing because we won't
> break every setup like 0.2.0 did and we will have a better feedback.
>
> J-D
>
> On Fri, Aug 22, 2008 at 12:43 PM, Daniel Leffel
> <da...@gmail.com>wrote:
>
> > I'm a little concerned that given the higher number of folks working
> > against the Hadoop effort, that the hbase developers will spin a lot
> > of wheels just keeping up with Hadoop releases and that feature
> > development will suffer. Is that a concern?
> >
> > On 8/22/08, Jean-Daniel Cryans <jd...@gmail.com> wrote:
> > > Good idea, but I would go farther. I think we should feature freeze as
> > soon
> > > as the equivalent Hadoop release is RC. Then the HBase RC would go out
> > with
> > > the official Hadoop release so that shields us from any bug in Hadoop.
> > >
> > > We should also more carefully select which feature should go into which
> > > version. Currently it's pretty much the Far West but that's
> > understandable
> > > since 0.2 took so long to ship. The team is growing, it's time to
> > structure.
> > >
> > >
> > > J-D
> > >
> > >
> > > On Fri, Aug 22, 2008 at 12:34 PM, Jim Kellerman <ji...@powerset.com>
> > wrote:
> > >
> > > > I do not want to get HBase as far behind the curve as we were with
> > 0.2.0.Until that release, there was no version of HBase that worked with
> > > > hadoop-0.17.x.
> > > >
> > > > What I'd like to do in the future is feature freeze HBase when a new
> > Hadoop
> > > > release comes out, apply only bug fixes and release a new HBase as
> > soon as
> > > > possible after Hadoop releases.
> > > >
> > > > Any features not included in a release will be included in the next
> > one. In
> > > > this way, there will always be a version of HBase that works with each
> > > > released version of Hadoop shortly after the Hadoop release.
> > > >
> > > > ---
> > > > Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> > > >
> > > > > -----Original Message-----
> > > > > From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of
> > > > stack
> > > > > Sent: Thursday, August 21, 2008 7:08 PM
> > > > > To: hbase-user@hadoop.apache.org
> > > > > Subject: Re: [Announcement] hbase-0.18.0 is now feature frozen
> > > > >
> > > > > And if you mean 0.3.0 is feature-frozen, as Rong-en asks, shouldn't
> > we
> > > > > discuss first before calling it feature-complete?
> > > > >
> > > > > St.Ack
> > > > >
> > > > >
> > > > > On Thu, Aug 21, 2008 at 6:18 PM, Rong-en Fan <gr...@gmail.com>
> > wrote:
> > > > >
> > > > > > Do you mean HBase-0.3.0??
> > > > > >
> > > > > > On Fri, Aug 22, 2008 at 6:45 AM, Jim Kellerman <ji...@powerset.com>
> > > > wrote:
> > > > > > > Since hadoop-0.18 is now available, hbase-0.18.0 is now feature
> > > > frozen.
> > > > > > >
> > > > > > > The only changes that will be accepted until hbase-0.18.0 is
> > released
> > > > are
> > > > > > blocker level bug fixes.
> > > > > > >
> > > > > > > I will be moving Jiras for feature requests from 0.18.0 to
> > 0.19.0
> > > > > > >
> > > > > > > ---
> > > > > > > Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> > >
> >
Re: [Announcement] hbase-0.18.0 is now feature frozen
Posted by Jean-Daniel Cryans <jd...@gmail.com>.
Well we still have to support every new Hadoop release but this will mean
fewer features in each release. In a way it's a good thing because we won't
break every setup like 0.2.0 did and we will have a better feedback.
J-D
On Fri, Aug 22, 2008 at 12:43 PM, Daniel Leffel <da...@gmail.com>wrote:
> I'm a little concerned that given the higher number of folks working
> against the Hadoop effort, that the hbase developers will spin a lot
> of wheels just keeping up with Hadoop releases and that feature
> development will suffer. Is that a concern?
>
> On 8/22/08, Jean-Daniel Cryans <jd...@gmail.com> wrote:
> > Good idea, but I would go farther. I think we should feature freeze as
> soon
> > as the equivalent Hadoop release is RC. Then the HBase RC would go out
> with
> > the official Hadoop release so that shields us from any bug in Hadoop.
> >
> > We should also more carefully select which feature should go into which
> > version. Currently it's pretty much the Far West but that's
> understandable
> > since 0.2 took so long to ship. The team is growing, it's time to
> structure.
> >
> >
> > J-D
> >
> >
> > On Fri, Aug 22, 2008 at 12:34 PM, Jim Kellerman <ji...@powerset.com>
> wrote:
> >
> > > I do not want to get HBase as far behind the curve as we were with
> 0.2.0.Until that release, there was no version of HBase that worked with
> > > hadoop-0.17.x.
> > >
> > > What I'd like to do in the future is feature freeze HBase when a new
> Hadoop
> > > release comes out, apply only bug fixes and release a new HBase as
> soon as
> > > possible after Hadoop releases.
> > >
> > > Any features not included in a release will be included in the next
> one. In
> > > this way, there will always be a version of HBase that works with each
> > > released version of Hadoop shortly after the Hadoop release.
> > >
> > > ---
> > > Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> > >
> > > > -----Original Message-----
> > > > From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of
> > > stack
> > > > Sent: Thursday, August 21, 2008 7:08 PM
> > > > To: hbase-user@hadoop.apache.org
> > > > Subject: Re: [Announcement] hbase-0.18.0 is now feature frozen
> > > >
> > > > And if you mean 0.3.0 is feature-frozen, as Rong-en asks, shouldn't
> we
> > > > discuss first before calling it feature-complete?
> > > >
> > > > St.Ack
> > > >
> > > >
> > > > On Thu, Aug 21, 2008 at 6:18 PM, Rong-en Fan <gr...@gmail.com>
> wrote:
> > > >
> > > > > Do you mean HBase-0.3.0??
> > > > >
> > > > > On Fri, Aug 22, 2008 at 6:45 AM, Jim Kellerman <ji...@powerset.com>
> > > wrote:
> > > > > > Since hadoop-0.18 is now available, hbase-0.18.0 is now feature
> > > frozen.
> > > > > >
> > > > > > The only changes that will be accepted until hbase-0.18.0 is
> released
> > > are
> > > > > blocker level bug fixes.
> > > > > >
> > > > > > I will be moving Jiras for feature requests from 0.18.0 to
> 0.19.0
> > > > > >
> > > > > > ---
> > > > > > Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> > > > > >
> > > > > >
> > > > >
> > >
> >
>
Re: [Announcement] hbase-0.18.0 is now feature frozen
Posted by Andrew Purtell <ap...@yahoo.com>.
> From: Daniel Leffel <da...@gmail.com>
> Subject: Re: [Announcement] hbase-0.18.0 is now feature frozen
> To: hbase-user@hadoop.apache.org
> Date: Friday, August 22, 2008, 9:43 AM
> I'm a little concerned that given the higher number of
> folks working against the Hadoop effort, that the hbase
> developers will spin a lot of wheels just keeping up with
> Hadoop releases and that feature development will suffer. Is
> that a concern?
That's actually an argument for +1 for a synchronized release
schedule I think. Lately it has been difficult to keep up with
all of the subprojects of Hadoop trunk, at least for me. Given
that level of development and new feature integration it's not
unreasonable to assume that every Hadoop release will include
something that affects the stability and/or function of HBase.
DFS and the FS abstraction layer work comes to mind first and
foremost. However there are also task scheduler changes and
resource management frameworks that might impact or be useful
for TableMap and TableReduce. Also maybe HBase can/should
integrate with the Chukwa monitoring framework
(https://issues.apache.org/jira/browse/HADOOP-3719). Etc...
- Andy
Re: [Announcement] hbase-0.18.0 is now feature frozen
Posted by Daniel Leffel <da...@gmail.com>.
I'm a little concerned that given the higher number of folks working
against the Hadoop effort, that the hbase developers will spin a lot
of wheels just keeping up with Hadoop releases and that feature
development will suffer. Is that a concern?
On 8/22/08, Jean-Daniel Cryans <jd...@gmail.com> wrote:
> Good idea, but I would go farther. I think we should feature freeze as soon
> as the equivalent Hadoop release is RC. Then the HBase RC would go out with
> the official Hadoop release so that shields us from any bug in Hadoop.
>
> We should also more carefully select which feature should go into which
> version. Currently it's pretty much the Far West but that's understandable
> since 0.2 took so long to ship. The team is growing, it's time to structure.
>
>
> J-D
>
>
> On Fri, Aug 22, 2008 at 12:34 PM, Jim Kellerman <ji...@powerset.com> wrote:
>
> > I do not want to get HBase as far behind the curve as we were with 0.2.0.Until that release, there was no version of HBase that worked with
> > hadoop-0.17.x.
> >
> > What I'd like to do in the future is feature freeze HBase when a new Hadoop
> > release comes out, apply only bug fixes and release a new HBase as soon as
> > possible after Hadoop releases.
> >
> > Any features not included in a release will be included in the next one. In
> > this way, there will always be a version of HBase that works with each
> > released version of Hadoop shortly after the Hadoop release.
> >
> > ---
> > Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> >
> > > -----Original Message-----
> > > From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of
> > stack
> > > Sent: Thursday, August 21, 2008 7:08 PM
> > > To: hbase-user@hadoop.apache.org
> > > Subject: Re: [Announcement] hbase-0.18.0 is now feature frozen
> > >
> > > And if you mean 0.3.0 is feature-frozen, as Rong-en asks, shouldn't we
> > > discuss first before calling it feature-complete?
> > >
> > > St.Ack
> > >
> > >
> > > On Thu, Aug 21, 2008 at 6:18 PM, Rong-en Fan <gr...@gmail.com> wrote:
> > >
> > > > Do you mean HBase-0.3.0??
> > > >
> > > > On Fri, Aug 22, 2008 at 6:45 AM, Jim Kellerman <ji...@powerset.com>
> > wrote:
> > > > > Since hadoop-0.18 is now available, hbase-0.18.0 is now feature
> > frozen.
> > > > >
> > > > > The only changes that will be accepted until hbase-0.18.0 is released
> > are
> > > > blocker level bug fixes.
> > > > >
> > > > > I will be moving Jiras for feature requests from 0.18.0 to 0.19.0
> > > > >
> > > > > ---
> > > > > Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> > > > >
> > > > >
> > > >
> >
>
Re: [Announcement] hbase-0.18.0 is now feature frozen
Posted by Jean-Daniel Cryans <jd...@gmail.com>.
Good idea, but I would go farther. I think we should feature freeze as soon
as the equivalent Hadoop release is RC. Then the HBase RC would go out with
the official Hadoop release so that shields us from any bug in Hadoop.
We should also more carefully select which feature should go into which
version. Currently it's pretty much the Far West but that's understandable
since 0.2 took so long to ship. The team is growing, it's time to structure.
J-D
On Fri, Aug 22, 2008 at 12:34 PM, Jim Kellerman <ji...@powerset.com> wrote:
> I do not want to get HBase as far behind the curve as we were with 0.2.0.Until that release, there was no version of HBase that worked with
> hadoop-0.17.x.
>
> What I'd like to do in the future is feature freeze HBase when a new Hadoop
> release comes out, apply only bug fixes and release a new HBase as soon as
> possible after Hadoop releases.
>
> Any features not included in a release will be included in the next one. In
> this way, there will always be a version of HBase that works with each
> released version of Hadoop shortly after the Hadoop release.
>
> ---
> Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
>
> > -----Original Message-----
> > From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of
> stack
> > Sent: Thursday, August 21, 2008 7:08 PM
> > To: hbase-user@hadoop.apache.org
> > Subject: Re: [Announcement] hbase-0.18.0 is now feature frozen
> >
> > And if you mean 0.3.0 is feature-frozen, as Rong-en asks, shouldn't we
> > discuss first before calling it feature-complete?
> >
> > St.Ack
> >
> >
> > On Thu, Aug 21, 2008 at 6:18 PM, Rong-en Fan <gr...@gmail.com> wrote:
> >
> > > Do you mean HBase-0.3.0??
> > >
> > > On Fri, Aug 22, 2008 at 6:45 AM, Jim Kellerman <ji...@powerset.com>
> wrote:
> > > > Since hadoop-0.18 is now available, hbase-0.18.0 is now feature
> frozen.
> > > >
> > > > The only changes that will be accepted until hbase-0.18.0 is released
> are
> > > blocker level bug fixes.
> > > >
> > > > I will be moving Jiras for feature requests from 0.18.0 to 0.19.0
> > > >
> > > > ---
> > > > Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> > > >
> > > >
> > >
>
RE: [Announcement] hbase-0.18.0 is now feature frozen
Posted by Jim Kellerman <ji...@powerset.com>.
I do not want to get HBase as far behind the curve as we were with 0.2.0. Until that release, there was no version of HBase that worked with hadoop-0.17.x.
What I'd like to do in the future is feature freeze HBase when a new Hadoop release comes out, apply only bug fixes and release a new HBase as soon as possible after Hadoop releases.
Any features not included in a release will be included in the next one. In this way, there will always be a version of HBase that works with each released version of Hadoop shortly after the Hadoop release.
---
Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> -----Original Message-----
> From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of stack
> Sent: Thursday, August 21, 2008 7:08 PM
> To: hbase-user@hadoop.apache.org
> Subject: Re: [Announcement] hbase-0.18.0 is now feature frozen
>
> And if you mean 0.3.0 is feature-frozen, as Rong-en asks, shouldn't we
> discuss first before calling it feature-complete?
>
> St.Ack
>
>
> On Thu, Aug 21, 2008 at 6:18 PM, Rong-en Fan <gr...@gmail.com> wrote:
>
> > Do you mean HBase-0.3.0??
> >
> > On Fri, Aug 22, 2008 at 6:45 AM, Jim Kellerman <ji...@powerset.com> wrote:
> > > Since hadoop-0.18 is now available, hbase-0.18.0 is now feature frozen.
> > >
> > > The only changes that will be accepted until hbase-0.18.0 is released are
> > blocker level bug fixes.
> > >
> > > I will be moving Jiras for feature requests from 0.18.0 to 0.19.0
> > >
> > > ---
> > > Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> > >
> > >
> >
Re: [Announcement] hbase-0.18.0 is now feature frozen
Posted by stack <st...@duboce.net>.
And if you mean 0.3.0 is feature-frozen, as Rong-en asks, shouldn't we
discuss first before calling it feature-complete?
St.Ack
On Thu, Aug 21, 2008 at 6:18 PM, Rong-en Fan <gr...@gmail.com> wrote:
> Do you mean HBase-0.3.0??
>
> On Fri, Aug 22, 2008 at 6:45 AM, Jim Kellerman <ji...@powerset.com> wrote:
> > Since hadoop-0.18 is now available, hbase-0.18.0 is now feature frozen.
> >
> > The only changes that will be accepted until hbase-0.18.0 is released are
> blocker level bug fixes.
> >
> > I will be moving Jiras for feature requests from 0.18.0 to 0.19.0
> >
> > ---
> > Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> >
> >
>
Re: [Announcement] hbase-0.18.0 is now feature frozen
Posted by Rong-en Fan <gr...@gmail.com>.
Do you mean HBase-0.3.0??
On Fri, Aug 22, 2008 at 6:45 AM, Jim Kellerman <ji...@powerset.com> wrote:
> Since hadoop-0.18 is now available, hbase-0.18.0 is now feature frozen.
>
> The only changes that will be accepted until hbase-0.18.0 is released are blocker level bug fixes.
>
> I will be moving Jiras for feature requests from 0.18.0 to 0.19.0
>
> ---
> Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
>
>