+1 on thrift interface + EC2 scripts in the core, as they will be very
useful to bootstrap hbase.
Being another independent app service provider by itself - not sure if
REST connectors can be categorized as a core functionality to the
architecture.
On 01/30/2010 08:23 PM, Ryan Rawson wrote:
We use and need thrift. So count me in on that.
On Jan 30, 2010 8:18 PM, "Andrew Purtell"<apurt...@apache.org> wrote:
I agree and think that's the definition of core. So the committers need to
agree either:
1) Someone steps up to concentrate on some area/former contrib no matter
what the problem
I will do this for the "Stargate" REST connector and the EC2 scripts
(which should just go into bin/cloud/ I guess). I have already been
doing this.
2) All committers agree to support something as needed.
For me: Thrift connector, REST connector, EC2 scripts; no problem
Not sure about IHBase or THBase. I think we would need to choose one or
neither.
I'd say we opt for #2 style agreement if someone does not feel comfortable
with the #1 style agreement, but in my opinion as long as a committer says
they will take care of something, that's good enough for me.
- Andy
----- Original Message ----
From: Ryan Rawson<ryano...@gmail.com>
To: hbase-...@hadoop.apach...
Sent: Sun, January 31, 2010 9:03:56 AM
Subject: Re: Discussion: Move contribs out of hbase?
What does it take to move a contrib into core?
I would think that a committer must be able to...
