Since contract has attributes such NUMBER, TOTAL, ACCOUNT and soon When doing the follow:
row_key || CF: Contract --------------------------------------------------------------------- valter || 'C11' | info_for_11 | 'C12' | info_for_12 ---------------------------------------------------------------------- info_for_NN should be comma-separeted values, xml, a serialized java object? On CF for contract attribute? Thanks, Valter 2010/12/28 Sean Bigdatafun <[email protected]> > 1. customer_table: > row_key --> column_family : (customer --> contract) > > An example row, > row_key || CF: Contract > --------------------------------------------------------------------- > valter || 'C11' | info_for_11 | 'C12' | info_for_12 > ---------------------------------------------------------------------- > > > 2. contract_table: > row_key --> column_family (contract_id --> installment) > > An example row, > row_key || CF: Installment > > ----------------------------------------------------------------------------------------- > C11 || 'I_1001' | info_for_1001 | 'I_1002' | info_for_1002 > > ---------------------------------------------------------------------------------------- > > > On Tue, Dec 28, 2010 at 3:26 PM, Valter Nogueira <[email protected] > >wrote: > > > I have a small JAVA system using relational database. > > > > Basically, the app have 3 entities: CUSTOMER has many CONTRACTs and each > > CONTRACT has many INSTALLMENTS > > > > Very classic. > > > > I am figuring out what is the best approach to convert it to HBASE. > > > > One way is to create a schema that mimics the relational schema. > > > > Other is saving INSTALLMENTS into the CONTRACT table. > > > > I would like some advice on doing this. > > > > Thanks, > > > > Valter > > > > > > -- > --Sean >
