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 C738F75D6 for ; Mon, 7 Nov 2011 16:36:38 +0000 (UTC) Received: (qmail 47289 invoked by uid 500); 7 Nov 2011 16:36:37 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 47195 invoked by uid 500); 7 Nov 2011 16:36:37 -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 47187 invoked by uid 99); 7 Nov 2011 16:36:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Nov 2011 16:36:37 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates 209.85.160.169 as permitted sender) Received: from [209.85.160.169] (HELO mail-gy0-f169.google.com) (209.85.160.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Nov 2011 16:36:29 +0000 Received: by gyg10 with SMTP id 10so7167481gyg.14 for ; Mon, 07 Nov 2011 08:36:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=X2PmBKfbK56MjfSnXH1kWZzDVNN54xWToN4sk1QdZLg=; b=HhA3mki+l4UpCDX7H8B9k1JL+JCOBp1a6Uh3jctiW5d/s9po9RC+/KkyvX4AK+IN1C DbXbG0ROSI6+09XoaXvS7kgBry01YIsPYL5sh0GT/CZy0BRioA9Dv8KcFm0S8kAbxCAN YsHKXcl8ZeRr9Fm8uNMvPGGSuyWfqiKcmZRSU= MIME-Version: 1.0 Received: by 10.101.7.23 with SMTP id k23mr5988625ani.76.1320683767961; Mon, 07 Nov 2011 08:36:07 -0800 (PST) Sender: jdcryans@gmail.com Received: by 10.100.48.12 with HTTP; Mon, 7 Nov 2011 08:36:07 -0800 (PST) In-Reply-To: References: Date: Mon, 7 Nov 2011 16:36:07 +0000 X-Google-Sender-Auth: JXAPCyqGaswrrDAIbiyDAZN6JIU Message-ID: Subject: Re: multiple rows with same unique row+dynamic update From: Jean-Daniel Cryans To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org You might want to (re)read this: http://hbase.apache.org/book/versions.html There's no conflict. J-D On Mon, Nov 7, 2011 at 4:24 PM, Jignesh Patel wrote: > Jean, > Is that a new row or part of same row? And I believe this data will go > to new file. > Because my row id is still same:jigneshmpatel, shouldn't it create > conflict if it is a new version. > > -Jignesh > > On Mon, Nov 7, 2011 at 11:07 AM, Jean-Daniel Cryans wrote: >> column3name:Phone would have a new version, yes. >> >> On Mon, Nov 7, 2011 at 4:02 PM, Jignesh Patel wrote: >>> Is that new entry or update in HBase? >>> >>> -Jignesh >>> >>> On Mon, Nov 7, 2011 at 10:46 AM, Jean-Daniel Cryans wrote: >>>> ok that works... what's the issue? >>>> >>>> On Mon, Nov 7, 2011 at 3:44 PM, Jignesh Patel wrote: >>>>> I have say >>>>> uniqname(rowid) :jigneshmpatel >>>>> columnfamily:Data >>>>> comun1name: address 1: Value1 >>>>> comun2name:address2: value2 >>>>> column3name:Phone: 1234 >>>>> >>>>> and now after one week >>>>> >>>>> >>>>> uniqname(rowid) :jigneshmpatel >>>>> columnfamily:Data >>>>> comun1name: address 1: Value4 >>>>> comun2name:address2: value5 >>>>> column3name:Phone: 5678. >>>>> >>>>> -Jignesh >>>>> >>>>> On Mon, Nov 7, 2011 at 10:38 AM, Jean-Daniel Cryans wrote: >>>>>> What do you mean by dynamic update? Replace one value by another? >>>>>> HBase does that. >>>>>> >>>>>> J-D >>>>>> >>>>>> On Mon, Nov 7, 2011 at 3:29 PM, Jignesh Patel wrote: >>>>>>> Companies like Facebook and Stumble upon uses HBase for the day to day >>>>>>> transaction. Since HBase and HDFS both are not going to support >>>>>>> dynamic updates, how would they able to keep track of unique customer >>>>>>> id(which is normally row ID) in HBase? >>>>>>> >>>>>>> Also wanted to know is there a work-around to handle dynamic update? >>>>>>> >>>>>>> >>>>>>> -Jignesh >>>>>>> >>>>>> >>>>> >>>> >>> >> >