Mohit, The short answer is that the row key is the primary key and hence has a backing index. Outside of that, HBase doesn't support secondary indexes. Your primary key could be a composite of values.
You can use a secondary index, and some of the code is out in Git Hub. But its not supported by Apache or Cloudera. You could use a package like Lilly. You could roll your own. HTH -Mike > Date: Thu, 10 Mar 2011 21:22:14 +0530 > From: [email protected] > Subject: Query Regarding HBase Schema Design for Composite Keys and Indexing. > To: [email protected] > > Hello HBase Users/Authors, > > > > I may be digging old things out for which there could be lot of > debates/discussions, I couldn't able to get much info, I'm looking for > direct and precise answers. > > > > It is simple and complex/tricky at the same time. > > > > Ques1 :- Does HBase supports composite keys, If yes, any example to support > this. > > Ques2 :- Does HBase supports indexing based on this composite keys. > > Ques3 :- Did somebody tried to find out of curiosity; limitation on number > of indexes which can be created per table. > > > > Thanks for helping me out. > > > > --Mohit > > > > **************************************************************************** > *********** > This e-mail and 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! > > >
