Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Tue, 10 Nov 2009 16:07:29 +0100
From: Julien Ruchaud <julien.ruchaud@codelutin.com>
To: hbase-user@hadoop.apache.org
Subject: Re: Strore list
Message-ID: <20091110160729.38f716b3@eleonore.codelutin.home>
In-Reply-To: <31a243e70911100650p150645b2p4002cb037f7ffa12@mail.gmail.com>
References: <20091110104115.4db9d4e0@eleonore.codelutin.home>
	<31a243e70911100650p150645b2p4002cb037f7ffa12@mail.gmail.com>
Organization: Code Lutin
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Le Tue, 10 Nov 2009 06:50:46 -0800,
Jean-Daniel Cryans <jdcryans@apache.org> a =C3=A9crit :

> Julien,
>=20
> 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.=20
>=20
> 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 =3D value 1
key =3D value 2

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

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

d) other ...

Julien

>=20
> J-D
>=20
> 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
> >