hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: Schema Design
Date Wed, 29 Dec 2010 03:58:08 GMT
Consider using TableInputFormat.

For serialization, one more choice is Avro.

On Tue, Dec 28, 2010 at 4:46 PM, Valter Nogueira <vgnogueira@gmail.com>wrote:

> And what about searching such contents?
>
> How to search for overdued contracts?
>
> I could read every contract thru map-reduce, select overdued contracts and
> build a table with such contracts - is that the right approach?
>
> Valter
>
> 2010/12/28 Sean Bigdatafun <sean.bigdatafun@gmail.com>
>
> > I'd suggest json object, or xml, or any binary protocol buffer such as
> > Google PB, Facebook Thrift PB.
> >
> > If you use any of those, you will have much better control over version
> > upgrade
> >
> >
> >
> >
> > On Tue, Dec 28, 2010 at 4:16 PM, Valter Nogueira <vgnogueira@gmail.com
> > >wrote:
> >
> > > 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 <sean.bigdatafun@gmail.com>
> > >
> > > > 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 <
> vgnogueira@gmail.com
> > > > >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
> > > >
> > >
> >
> >
> >
> > --
> > --Sean
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message