[
https://issues.apache.org/jira/browse/HBASE-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141146#comment-14141146
]
Niels Basjes commented on HBASE-11990:
--------------------------------------
[~stack] Thanks.
I thought of a possibility to create good tests for hbase-client on my way home
today:
# We create an additional module in the top pom.xml called hbase-client-tests
# This module is the last module in the pom.xml so when it is executed all
modules (including hbase-server that has the HBaseTestingUtility) are available.
# This module does not have a src/main only a src/test and contains the real
tests for much of the hbase-client stuff (Like doing real scans with filters)
This means that the hbase-client is packaged and installed without being
tested.
However the build as a whole does fail if one or more of the tests fail.
I haven't tried anything like this yet so I'm not quite sure it will work.
What do you guys think, worth a try?
> 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: 11990v4.txt, HBASE-11990-20140916-v2.patch,
> HBASE-11990-20140916-v3.patch, HBASE-11990-20140916-v5.patch,
> HBASE-11990-20140916-v6.patch, HBASE-11990-20140916.patch,
> HBASE-11990-20140917-v7.patch, HBASE-11990-20140919-v8.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 }{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)
