Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 16 Sep 2014 16:14:34 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12741724.1410859108000.45575.1410884074493@Atlassian.JIRA>
In-Reply-To: <JIRA.12741724.1410859108000@Atlassian.JIRA>
References: <JIRA.12741724.1410859108000@Atlassian.JIRA>
 <JIRA.12741724.1410859108804@arcas>
Subject: [jira] [Commented] (HBASE-11990) Make setting the start and stop
 row for a specific prefix easier
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135654#comment-14135654 ] 

stack commented on HBASE-11990:
-------------------------------

Use case and patch look good to me.  I'd add an example to the javadoc -- the description on this issue would do -- to the new methods to make it more clear what the behavior is.

> Make setting the start and stop row for a specific prefix easier
> ----------------------------------------------------------------
>
>                 Key: HBASE-11990
>                 URL: https://issues.apache.org/jira/browse/HBASE-11990
>             Project: HBase
>          Issue Type: New Feature
>          Components: Client
>            Reporter: Niels Basjes
>         Attachments: HBASE-11990-20140916.patch
>
>
> If you want to set a scan from your application to scan for a specific row prefix this is actually quite hard.
> As described in several places you can set the startRow to the prefix; yet the stopRow should be set to the prefix '+1'
> If the prefix 'ASCII' put into a byte[] then this is easy because you can simply increment the last byte of the array. 
> But if your application uses real binary rowids you may run into the scenario that your prefix is something like 
> {code}{ 0x12, 0x23, 0xFF, 0xFF }{code} Then the increment should be {code}{ 0x12, 0x24, 0x00, 0x00 }{code}
> I have prepared a proposed patch that makes setting these values correctly a lot easier.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)