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 E9C2EDAFB for ; Fri, 16 Nov 2012 07:33:30 +0000 (UTC) Received: (qmail 37813 invoked by uid 500); 16 Nov 2012 07:33:28 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 37737 invoked by uid 500); 16 Nov 2012 07:33:28 -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 37699 invoked by uid 99); 16 Nov 2012 07:33:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Nov 2012 07:33:28 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates 209.85.219.41 as permitted sender) Received: from [209.85.219.41] (HELO mail-oa0-f41.google.com) (209.85.219.41) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Nov 2012 07:33:20 +0000 Received: by mail-oa0-f41.google.com with SMTP id k14so3063413oag.14 for ; Thu, 15 Nov 2012 23:32:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=XL3+QjPj4kbyzlanCBnO7gbFcg68PGQbHg8yUZBRdPM=; b=vxdI4gx1hggkyKTKQpLnPfn610Tkos2HgyvlmU3+c59tDER37Ti1kk7gfy1r2wWrxe Rgw9Ruydse0Gnxvl2NVKNr8Xq9K3BWSq40FfpJYpy92EjbOdD2TuXRnC77bx8Mr7zQZW Cvec3WBJGeIJo59QtZT9HHu1oUKZQT29ckzJnbAvpbTCK9k12HRzCxACV8bRPfUl+Ylg IzowHyqi4Ud1vhQvOdhmm26g/MKy4uvBNCdfmnIwvo3XIoyAUmzZ5mamQjwIz0uZmHZm 3w4xM+dHDw7Puqp6jdjlgb7j9NN8zbjb0aLwKNb1EAnLLTXE7+EGT1Cc/hU+JAifh3yV 3Grg== MIME-Version: 1.0 Received: by 10.60.171.11 with SMTP id aq11mr3099388oec.104.1353051179067; Thu, 15 Nov 2012 23:32:59 -0800 (PST) Sender: saint.ack@gmail.com Received: by 10.76.152.231 with HTTP; Thu, 15 Nov 2012 23:32:58 -0800 (PST) In-Reply-To: <1353046323077-4034076.post@n3.nabble.com> References: <1352969011060-4034028.post@n3.nabble.com> <0CE69E9126D0344088798A3B7F7F80863AE9520C@SZXEML553-MBX.china.huawei.com> <1353046323077-4034076.post@n3.nabble.com> Date: Thu, 15 Nov 2012 23:32:58 -0800 X-Google-Sender-Auth: 9_KaaETzSAc3GeVDw9x9djReQwY Message-ID: Subject: Re: Hbase Region Split not working with JAVA API From: Stack To: Hbase-User Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Nov 15, 2012 at 10:12 PM, msmdhussain wrote: > > i tried using the follwing command in hbase shell > >>> put >>> 'Test','\x03\x00\x00\x00\x0A\x00\x00\x01:K\xF0\xC0@IN\x00\x00AS*******','C:input','25' > > but, row key length is 292 bytes its a composite key combination of > time_seg+date+country_id+****+metrics_id (15 fields) > > it is stored in the correct region '\x03' > > and im converting all the above field values into byte in java program and > using the Put java api to insert the value to the hbase > > but, it get stored in the first region '\x01' > > i dont know why its happening when using java api Your translation of region name must be incorrect. It can be tricky going from the String representation to the raw bytes. Can you do something like figure out its ordinal position in .META. then scan .META. The rows in .META. are regionnames. You can take the Nth row in the .META. and use its bytes as the region name doing your manipulations? St.Ack