Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 63134 invoked from network); 5 Apr 2011 16:21:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Apr 2011 16:21:41 -0000 Received: (qmail 51885 invoked by uid 500); 5 Apr 2011 16:21:39 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 51819 invoked by uid 500); 5 Apr 2011 16:21:39 -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 51777 invoked by uid 99); 5 Apr 2011 16:21:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Apr 2011 16:21:34 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.220.169 as permitted sender) Received: from [209.85.220.169] (HELO mail-vx0-f169.google.com) (209.85.220.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Apr 2011 16:21:27 +0000 Received: by vxk20 with SMTP id 20so597940vxk.14 for ; Tue, 05 Apr 2011 09:21:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=ybLGfuUSFCB0AfFNAWAC4jWfXZrCi/nCu1ieL1sa8eU=; b=i2t/9Ef0wOIjEPRXcRroDLC9fH74k7CgIyIhT1vvNNqypVqmFPjQr6Xg1olRD+W1aG NH+nnuaBst3yAkUAjoYf5LbEohGd7ntVbepDy7t7FcnVhwdzXwpx38q2T2x1Y9g1KmFs Q61ot3srWrqxHZaeYcDfDxnjn+DuB2Uwqmmnc= DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=P0t3GmV6m6EO/9WtZMOZj+z58nxyfKK/TMQVKvmZJq0g610RghZRSnmykAAPgGfqhF +TDL93GYcYgFiLasn5gZjLv/2LXR4GQa+IKCorQpaE/pe1GorvXUCUbY/joKhgKa4wxl 695vKWoAX5+XwP4nEwwMmVg3hcayzRLVnWpPI= MIME-Version: 1.0 Received: by 10.52.89.82 with SMTP id bm18mr11412462vdb.99.1302020467069; Tue, 05 Apr 2011 09:21:07 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.52.188.164 with HTTP; Tue, 5 Apr 2011 09:21:07 -0700 (PDT) In-Reply-To: References: Date: Tue, 5 Apr 2011 09:21:07 -0700 X-Google-Sender-Auth: qIGu5gtnTKcrkh-_XRZCLz2Mep0 Message-ID: Subject: Re: Changing the key in Hbase From: Stack To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Tue, Apr 5, 2011 at 12:41 AM, Anand wrote: > Hi, > > I have a case in which i have to change the keys for the values inserted in > hbase. The cluster is having some 200 million urls. Earlier we have inserted the > keys by constructing 128 bit hash code for the key string. Now i have to change > the key alone for those records by changing them into 64 bit hash code and > maintain the values. Is there any other way to do this other than getting all > the values one by one and creating a new key and adding the old value to it and > reinserting?? > Yes. You'll have to reinsert. St.Ack