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 3F47011AEA for ; Thu, 27 Mar 2014 12:46:55 +0000 (UTC) Received: (qmail 47350 invoked by uid 500); 27 Mar 2014 12:46:51 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 46823 invoked by uid 500); 27 Mar 2014 12:46:50 -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 46814 invoked by uid 99); 27 Mar 2014 12:46:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2014 12:46:50 +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 yuzhihong@gmail.com designates 209.85.220.48 as permitted sender) Received: from [209.85.220.48] (HELO mail-pa0-f48.google.com) (209.85.220.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2014 12:46:43 +0000 Received: by mail-pa0-f48.google.com with SMTP id hz1so3429697pad.7 for ; Thu, 27 Mar 2014 05:46:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=9ZEafl9Jo6UMiybOYTRUpL+0pQwhqTqbGBIvEFWNEzI=; b=hvQeZTFhMcYX0WPu7Wm3fxY6/XFEtm61NGNnbZPQ+Um4bIuGy1W5SBDQlOdQ7y2fYl a/yrqNFV/MswyY2tmLYQwdeYPXwU/WhTjsA5cbNGex8sHgYED6VZS/BoI0Hp6Qj2oRd5 awtGs+GYX5cwSjAohnCFxM016/MI3WMm+xJTSHqY2jAJHyLT1J8cWs+AXWaiUjunE+xG /Qw3dH7V6AJRqFqpsf6Melu2XZ5kVWW4P7ZYYHtfvNulQdY4hNwo4dOdZCPhneKAfhVa 5/o2RvWsZByIaFRdH8CB7EbQOx1sSqpbyK3yoxSaQKTff2YeAZUEO0QS/PFrly575jA0 45/g== X-Received: by 10.66.66.202 with SMTP id h10mr1657207pat.70.1395924381943; Thu, 27 Mar 2014 05:46:21 -0700 (PDT) Received: from [192.168.0.13] (c-24-130-236-83.hsd1.ca.comcast.net. [24.130.236.83]) by mx.google.com with ESMTPSA id pp5sm8612551pbb.33.2014.03.27.05.46.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Mar 2014 05:46:21 -0700 (PDT) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Cc: hbase-user X-Mailer: iPhone Mail (10B146) From: Ted Yu Subject: Re: how to reverse an integer for rowkey? Date: Thu, 27 Mar 2014 05:46:20 -0700 To: "user@hbase.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org Reverse scan is slower compared to forward scan.=20 Depending on access pattern, storing int field in decreasing order may be de= sirable.=20 Cheers On Mar 27, 2014, at 4:54 AM, haosdent wrote: > 0.94 also support reverse scan. >=20 > https://issues.apache.org/jira/browse/HBASE-4811?focusedCommentId=3D138393= 23&page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#c= omment-13839323 >=20 >=20 > On Thu, Mar 27, 2014 at 4:58 PM, Li Li wrote: >=20 >> great feature but I am using 0.94 now >>=20 >> On Thu, Mar 27, 2014 at 4:49 PM, haosdent wrote: >>> How about Reverse Scan? https://issues.apache.org/jira/browse/HBASE-4811= >>>=20 >>>=20 >>> On Thu, Mar 27, 2014 at 4:24 PM, Li Li wrote: >>>=20 >>>> my rowkey is >>>> I want to scan it by decreasing order of the int field, how to make it >>>> reversed? >>>> if the row key is Bytes.toBytes(intField) + Bytes.toBytes(strField), >>>> then the order is increasing. >>>> one solution is replace intField with -intField. but if >>>> intField=3D=3DInteger.MIN_VALUE, what will happen? >>>=20 >>>=20 >>>=20 >>> -- >>> Best Regards, >>> Haosdent Huang >=20 >=20 >=20 > --=20 > Best Regards, > Haosdent Huang