hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dhruba Borthakur <dhr...@gmail.com>
Subject Re: [DISCUSS] HBase as Apache top-level project?
Date Thu, 18 Mar 2010 18:08:06 GMT
Hi Stack,

Can HBase (in theory) be used on filesystems/MR other than Hadoop?

I see one primary disadvantage of moving away from the Hadoop project.
Please let me explain. In the Hadoop world, if a committer is actively
contributing code, she/he becomes part of the Hadoop PMC. This means that
Hbase active hbase committers would (over time) become Hadoop PMC members.
This might allow Hbase-related fixes to get into HDFS much more easily. If
HBase moves away from Hadoop, then Hbase developers will not have a part to
play in guiding HDFS to make it more amenable to HBase usage.

The case is different for ZK and avro. They are not related to Hadoop
HDFS/MR at all.

I am not voting against this proposal, just laying out my viewpoint.

thanks,
dhruba


On Thu, Mar 18, 2010 at 10:43 AM, Stack <stack@duboce.net> wrote:

> On Thu, Mar 18, 2010 at 10:15 AM, Andrew Purtell <apurtell@apache.org>
> wrote:
> >
> > HBase is an integrated optional part of a Hadoop stack more
> > than a standalone component, but other ASF TLPs build on top
> > of other projects. I suppose HDFS and ZK are going to be TLPs
> > at some point also, is that true? Leaving Hadoop as just the
> > MR framework?
>
> If the board allows us be a TLP, Zookeeper would probably be made a
> TLP at same time.
>
> There hasn't been a vote, but it seems that the thought is that HDFS
> would stay within the hadoop fold; i.e. hdfs+mapreduce+common would
> stay.
>
> >
> > Anyway, what I like is HBase will stand on its own merits.
> >
> > What are the risks of being a TLP?
> >
>
> I'm sure there are some but I'm blinded by the upside at the moment.
>
> St.Ack
>



-- 
Connect to me at http://www.facebook.com/dhruba

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