Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0CBCA106A7 for ; Fri, 24 Jan 2014 19:36:55 +0000 (UTC) Received: (qmail 41015 invoked by uid 500); 24 Jan 2014 19:36:46 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 40662 invoked by uid 500); 24 Jan 2014 19:36:46 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 40534 invoked by uid 99); 24 Jan 2014 19:36:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jan 2014 19:36:45 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [64.78.52.101] (HELO pfe111-vx-1.mail.splunk.com) (64.78.52.101) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jan 2014 19:36:41 +0000 Received: from PMBX111-W1-VX-2.pexch111.serverpod.net ([10.254.185.52]) by PFE111-VX-1.pexch111.serverpod.net ([10.254.185.16]) with mapi id 14.03.0158.001; Fri, 24 Jan 2014 11:36:16 -0800 From: Sagar Naik To: "user@hbase.apache.org" Subject: Re: HBase Design : Column name v/s Version Thread-Topic: HBase Design : Column name v/s Version Thread-Index: AQHPGSmTPPQjbeBu1ECZatoW+9aDpZqUrG6A//9/i4CAAI1XAP//fZyAgAAKTPWAAAOXgA== Date: Fri, 24 Jan 2014 19:36:16 +0000 Message-ID: References: <1390585637.40880.YahooMailNeo@web190103.mail.sg3.yahoo.com> <1390588404.70450.YahooMailNeo@web190102.mail.sg3.yahoo.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [98.248.44.108] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org I do not have to purge the data. I always need all the versions. But Dhaval, raised a valid point of 100K versions and no pagination support based on versions. -Sagar On 1/24/14 11:23 AM, "Vladimir Rodionov" wrote: >One downside of using synthetic versions is you won't be able to use TTL, >which gives you automatic purge of stale data for free >Have you thought already how to purge old data? > >Best regards, >Vladimir Rodionov >Principal Platform Engineer >Carrier IQ, www.carrieriq.com >e-mail: vrodionov@carrieriq.com > >________________________________________ >From: Sagar Naik [snaik@splunk.com] >Sent: Friday, January 24, 2014 10:46 AM >To: user@hbase.apache.org; Dhaval Shah >Subject: Re: HBase Design : Column name v/s Version > >Thanks for clarifying, > >I will be using custom version numbers (auto incrementing on the client >side) and not timestamps. >Two clients do not update the same row > > >-Sagar > >On 1/24/14 10:33 AM, "Dhaval Shah" wrote: > >>I am talking about schema 2. Schema 1 would definitely work. Schema 2 can >>have the version collisions if you decide to use timestamps as versions >> >>Regards, >> >>Dhaval >> >> >>----- Original Message ----- >>From: Sagar Naik >>To: "user@hbase.apache.org" ; Dhaval Shah >> >>Cc: >>Sent: Friday, 24 January 2014 1:07 PM >>Subject: Re: HBase Design : Column name v/s Version >> >>I am not sure I understand you correctly. >>I assume you are talking abt schema 1. >>In this case I m appending the version number to the column name. >> >>The column_names are different (data_1/data_2) for value_1 and value_2 >>respectively. >> >> >>-Sagar >> >> >>On 1/24/14 9:47 AM, "Dhaval Shah" wrote: >> >>>Versions in HBase are timestamps by default. If you intend to continue >>>using the timestamps, what will happen when someone writes value_1 and >>>value_2 at the exact same time? >>> >>>Regards, >>> >>>Dhaval >>> >>> >>>----- Original Message ----- >>>From: Sagar Naik >>>To: "user@hbase.apache.org" >>>Cc: >>>Sent: Friday, 24 January 2014 12:27 PM >>>Subject: HBase Design : Column name v/s Version >>> >>>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> val= ue_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> v= alue_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 >>> >> > > >Confidentiality Notice: The information contained in this message, >including any attachments hereto, may be confidential and is intended to >be read only by the individual or entity to whom this message is >addressed. If the reader of this message is not the intended recipient or >an agent or designee of the intended recipient, please note that any >review, use, disclosure or distribution of this message or its >attachments, in any form, is strictly prohibited. If you have received >this message in error, please immediately notify the sender and/or >Notifications@carrieriq.com and delete or destroy any copy of this >message and its attachments.