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

Hadoop QA commented on HBASE-8063:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12575901/8063.addendum
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/5038//console

This message is automatically generated.
                
> Filter HFiles based on first/last key
> -------------------------------------
>
>                 Key: HBASE-8063
>                 URL: https://issues.apache.org/jira/browse/HBASE-8063
>             Project: HBase
>          Issue Type: Improvement
>          Components: Scanners
>    Affects Versions: 0.98.0
>            Reporter: Liang Xie
>            Assignee: Liang Xie
>             Fix For: 0.98.0
>
>         Attachments: 8063.addendum, HBASE-8063.txt, HBASE-8063-v2.txt, 
> HBASE-8063-v3.txt, HBASE-8063-v4.txt
>
>
> # hbase-5010 introduced a filter mechanism based on timerange hint
> # this jira is a placeholder just for keyrange hint: currently, low 
> layer(hfile reader) has first/last key getter methods already. we should 
> utilize this information to pre-filte hfiles while choosing scanners from 
> storefiles.
> It's just a raw thought right now, no patch available yet. I'll summit a 
> patch asap if it's reasonable, welcome to give some suggestions/comments:)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to