llpind,
investigate first how you usually access this data. As HBase works best
when accessing data records through a so-called unique row key, it may
change your whole application design.
Many people also put special indexes on different fields of a Hbase
table, just to figure out the relevant row key of a data set as a first
step in a query.
Would need more details to give better advice.
Bob
llpind schrieb:
> Hello all,
>
> Our company has been looking into Hadoop & HBase, and has decided to put up
> a test cluster. I've got Hadoop (0.19.1) with HBase cluster up and running
> on 4 boxes. Currently we store our data in an Oracle database; I'd like
> ideas on how I can model a specific set of tables into HBase.
>
> The current project has two tables with a many to many relationship. Need a
> way to go back and forth between these tables (e.g. given a record of tableA
> grab many records from tableB. and vice-versa). I would like your opinion
> on how I would go about designing a model for this in HBase. I'm assuming
> it would be most efficient in a single HBase table. Thanks.
>
