Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Sagar Naik <snaik@splunk.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Subject: HBase Design : Column name v/s Version
Thread-Topic: HBase Design : Column name v/s Version
Thread-Index: AQHPGSmTPPQjbeBu1ECZatoW+9aDpQ==
Date: Fri, 24 Jan 2014 17:27:36 +0000
Message-ID: <CF07E28E.4CAD%snaik@splunk.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <56DC6BE1D421B34BBEF04096D827FE39@internal>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,

I have a choice to maintain to data either in column values or as
versioned data.
This data is not a versioned copy per se.

The access pattern on this get all the data every time

So the schema choices are :
Schema 1:
1. column_name/qualifier =3D> data_1. column_value =3D> value_1
1.a. column_name/qualifier =3D> data_2. column_value =3D> value_2,value_2.a

1.b. column_name/qualifier =3D> data_3. column_value =3D> value_3

To get all the values for "data", I will have to use ColumnPrefixFilter
with prefix set "data"

Schema 2:
2. column_name/qualifier =3D> data. version=3D> 1, column_value =3D> value_=
1

2.a. column_name/qualifier =3D> data. version=3D> 2, column_value =3D>
value_2,value_2.a

2.b. column_name/qualifier =3D> data. version=3D> 3, column_value =3D> valu=
e_3
To get all the values for "data" , I will do a simple get operation to get
all the versions.

Number of versions can go from: 10 to 100K

Get operation perf should beat the Filter perf.
Comparing 100K values will be costly as the # versions increase.

I would like to know if there are drawbacks in going the version route.


-Sagar