hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julien Ruchaud <julien.ruch...@codelutin.com>
Subject Re: Strore list
Date Tue, 10 Nov 2009 15:07:29 GMT
Le Tue, 10 Nov 2009 06:50:46 -0800,
Jean-Daniel Cryans <jdcryans@apache.org> a écrit :

> Julien,
> 
> Depends on your usage pattern. For example a list with 100,000+ values
> where you only access one at a time (like to do joins) should be
> stored in family where the qualifier is the key and the value is
> either again the key or something more useful. 
> 
> If you have small lists that you use as a whole, you can consider
> serializing them in a single cell with something like JSON, YAML,
> protobuf, etc.

In fact, I can need both cases. My list can contain 3 or 1,000,000
values...

What would be the best compromise ?

In the first case, do you mean storing values like this ?

a) Is it possible something like that ?
key = value 1
key = value 2

b) Difficult to maintain (update, delete an element, ...)
key[1] = value 1
key[2] = value 2

c) ??
key1 = value 1, key2
key2 = value 2

d) other ...

Julien

> 
> J-D
> 
> On Tue, Nov 10, 2009 at 1:41 AM, Julien Ruchaud
> <julien.ruchaud@codelutin.com> wrote:
> > Hi all,
> >
> > How to store a list with hbase ? Do I have to serialize list to
> > bytes before storing or shall I put multi-values in colunm ? What
> > is the best way ?
> >
> > Thanks,
> >
> > Julien
> >

Mime
View raw message