Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of jgray@fb.com designates
 66.220.144.140 as permitted sender)
From: Jonathan Gray <jgray@fb.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>, "apurtell@apache.org"
	<apurtell@apache.org>
Subject: RE: what's the roadmap of secondary index of hbase?
Thread-Topic: what's the roadmap of secondary index of hbase?
Thread-Index: AcvUwYd6W2SvykU5SmixAGgK5W38swAnHaAAAAH/tQAADv7cwP//mTUAgACEF+A=
Date: Fri, 25 Feb 2011 20:43:19 +0000
Message-ID: 
 <4A2E351F553A2C4D89148CC937FA8182058541@SC-MBX02-1.TheFacebook.com>
References: 
 <4A2E351F553A2C4D89148CC937FA81820584E5@SC-MBX02-1.TheFacebook.com>
 <441192.96424.qm@web65501.mail.ac4.yahoo.com>
In-Reply-To: <441192.96424.qm@web65501.mail.ac4.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Cool.  Plans for a design phase that we can collaborate on?

> -----Original Message-----
> From: Andrew Purtell [mailto:apurtell@apache.org]
> Sent: Friday, February 25, 2011 12:35 PM
> To: dev@hbase.apache.org
> Subject: RE: what's the roadmap of secondary index of hbase?
>=20
> Hi Jon,
>=20
> We have a team of three in our Nanjing office considering this problem an=
d
> the guys you already know in Cupertino can get involved. If you'd like to
> influence what happens through write up or some shared volunteer effort,
> be advised we have something getting underway now.
>=20
> Best regards,
>=20
>     - Andy
>=20
> Problems worthy of attack prove their worth by hitting back.
>   - Piet Hein (via Tom White)
>=20
>=20
> --- On Fri, 2/25/11, Jonathan Gray <jgray@fb.com> wrote:
>=20
> > From: Jonathan Gray <jgray@fb.com>
> > Subject: RE: what's the roadmap of secondary index of hbase?
> > To: "dev@hbase.apache.org" <dev@hbase.apache.org>
> > Date: Friday, February 25, 2011, 12:25 PM I've started my write-up.
> > Hopefully will have it posted by Monday night.=A0 There's also some
> > people at FB who may want to work on this.
> >
> > There are a few different ways that secondary indexing can go so there
> > might be an opportunity to work on a few different mechanisms if many
> > people are interested in working on it.
> >
> > JG
> >
> > > -----Original Message-----
> > > From: Mingjie Lai [mailto:mjlai09@gmail.com]
> > > Sent: Friday, February 25, 2011 11:34 AM
> > > To: dev@hbase.apache.org
> > > Subject: Re: what's the roadmap of secondary index of
> > hbase?
> > >
> > >
> > > Just had a discussion regarding new secondary indexing
> > design with Jon Gray
> > > this Tuesday at HUG-12. He said he would write up a
> > wiki to describe his
> > > thoughts regarding design. In the meaning while, we
> > will have some
> > > resources to work on it starting from next week. So
> > there will be something
> > > happening soon.
> > >
> > > Thanks J-D. Yes, HBase-3340 will be the right jira to
> > keep track of. The new
> > > secondary indexing will be based on coprocessors.
> > Further discussion will be
> > > at HBase-3340. Comments are welcome.
> > >
> > > Thanks,
> > > Mingjie
> > >
> > >
> > > On 02/25/2011 10:36 AM, Jean-Daniel Cryans wrote:
> > > > There's this jira:
> > > > https://issues.apache.org/jira/browse/HBASE-3340
> > > >
> > > > But currently I don't know of anyone actively
> > working on the feature.
> > > >
> > > > J-D
> > > >
> > > > On Thu, Feb 24, 2011 at 11:56 PM, Zhou Shuaifeng
> > > > <zhoushuaifeng@huawei.com>
> > wrote:
> > > >> Hi,
> > > >>
> > > >> Is there any plan or roadmap of secondary
> > index in hbase?
> > > >>
> > > >>
> > > >>
> > > >> Zhou Shuaifeng(Frank)
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> This e-mail and its attachments contain
> > confidential information from
> > > >> HUAWEI, which is intended only for the person
> > or entity whose address
> > > >> is listed above. Any use of the information
> > contained herein in any
> > > >> way (including, but not limited to, total or
> > partial disclosure,
> > > >> reproduction, or dissemination) by persons
> > other than the intended
> > > >> recipient(s) is prohibited. If you receive
> > this e-mail in error,
> > > >> please notify the sender by phone or email
> > immediately and delete it!
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> >
>=20
>=20
>=20