This schema looks like a pretty reasonable one. It's worth noting though,
that there are some performance implications of using multiple column
families like this for every 1:many relationship in raw HBase. Each column
family is expensive to maintain.
You might find it helpful to take a look at the KijiSchema project (
www.kiji.org). It's built on HBase and Avro, supports typed fields, and
also allows you to define arbitrary logical column families (and change
column types) in a safe, evolvable way.
Your row key schema looks pretty reasonable. You can manage your row keys
however you want in Kiji (just concatenate the strings as you'd like), but
we're thinking about adding direct support for composite keys to the system
On Mon, Dec 24, 2012 at 2:10 AM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
> Yes, you can. You just have to extract those fields in advance so that you
> constitute the rowkey before actually putting the data in that particular
> row. Also, try to keep your rowkeys as short as possible and if possible
> try to use byte as row keys.
> Best Regards,
> On Mon, Dec 24, 2012 at 2:42 PM, Ramasubramanian Narayanan <
> [EMAIL PROTECTED]> wrote:
> > Hi,
> > Thanks for your reply...
> > Could you please help in answering my 3rd question...
> > regards,
> > Rams
> > On Mon, Dec 24, 2012 at 1:23 PM, Mohammad Tariq <[EMAIL PROTECTED]>
> > wrote:
> > > design a rowkey w.r.t the row that we populate? for
> > > > example, for specific rows I may have Columns A+B+C constitue a
> > > for
> > > > some other records IN THE SAME TABLE, column B+C+D can be used as a
> > > rowkey?
> > >