[ 
https://issues.apache.org/jira/browse/HADOOP-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548136
 ] 

Hadoop QA commented on HADOOP-2299:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12370880/inclusive-stop-row-v2.patch
against trunk revision r600771.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1252/testReport/
Findbugs warnings: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1252/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1252/artifact/trunk/build/test/checkstyle-errors.html
Console output: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1252/console

This message is automatically generated.

> [hbase] Support inclusive scans
> -------------------------------
>
>                 Key: HADOOP-2299
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2299
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: contrib/hbase
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>            Priority: Trivial
>         Attachments: inclusive-stop-row-v2.patch, inclusive-stop-row.patch
>
>
> The existing scanner interface excludes the end key from the result range. If 
> you actually want to do an inclusive scan for some reason, you would 
> currently have to guess at the key immediately after the end key, which is a 
> shoddy solution. 
> A new stoprow filter could be created that stops at the end key but also 
> returns it. Then, you could supply an extra parameter to getScanner to say 
> you want an inclusive scan.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to