[jira] [Commented] (HBASE-11646) Handle the MOB in compaction

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on HBASE-11646:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12668311/HBASE-11646-V6.diff
  against trunk revision .
  ATTACHMENT ID: 12668311

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

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified tests.

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

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

This message is automatically generated.

> Handle the MOB in compaction
> ----------------------------
>
>                 Key: HBASE-11646
>                 URL: https://issues.apache.org/jira/browse/HBASE-11646
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Compaction
>    Affects Versions: hbase-11339
>            Reporter: Jingcheng Du
>            Assignee: Jingcheng Du
>             Fix For: hbase-11339
>
>         Attachments: HBASE-11646-V2.diff, HBASE-11646-V3.diff, HBASE-11646-V4.diff, HBASE-11646-V5.diff, HBASE-11646-V6.diff, HBASE-11646.diff
>
>
> In the updated MOB design however, admins can set CF level thresholds that would force cell values > the threshold to use the MOB write path instead of the traditional path.  There are two cases where mobs need to interact with this threshold
> 1) How do we handle the case when the threshold size is changed?
> 2) Today, you can bulkload hfiles that contain MOBs.  These cells will work as normal inside hbase.  Unfortunately the cells with MOBs in them will never benefit form the MOB write path.
> The proposal here is to modify compaction in mob enabled cf's such that the threshold value is honored with compactions.  This handles case #1 -- elements that should be moved out of the normal hfiles get 'compacted' into refs and mob hfiles, and values that should be pulled into the cf get derefed and written out wholy in the compaction.  For case #2, we can maintain the same behavior and compaction would move data into the mob writepath/lifecycle.



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