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

Hadoop QA commented on HBASE-16405:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 0m 4s {color} 
| {color:red} Docker failed to build yetus/hbase:date2016-08-18. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12824287/HBASE-16405_V4.patch |
| JIRA Issue | HBASE-16405 |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/3138/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


This message was automatically generated.



> Change read path Bloom check to work with Cells with out any copy
> -----------------------------------------------------------------
>
>                 Key: HBASE-16405
>                 URL: https://issues.apache.org/jira/browse/HBASE-16405
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Compaction
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16405.patch, HBASE-16405_V2.patch, 
> HBASE-16405_V3.patch, HBASE-16405_V4.patch
>
>
> Currently the read path though it works with Cells, still does go with the 
> assumption that we need to copy the Cells to KeyValue's key format and then 
> use the byte[] version of hash() function to calculate the Bloom hash. In 
> case of incoming cell's being KeyValue type we try to use the 
> KeyValue.getKey(), KeyValue.getKeyOffset() APIs. With this sub-task we will 
> get rid of all those and things will work with Cells. 



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

Reply via email to