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

Andrew Purtell commented on HBASE-11339:
----------------------------------------

bq. You'd have to go back a bit to get one that explicitly depended on MR but 
they did exist. (e.g. pre dist log splitting we had a MR based log replay – 
useful in avoiding 10 hr recovery downtimes).

The master's built in splitting was still available even if there was no MR 
runtime that could run the replay tool.

bq. What is your definition of stages? -- do you mean patch a time or something 
more like: stage one with external compactions, stage 2 with internal 
compactions? 

Stage = JIRA issue.

bq. For this MOB feature, we would have the experimental tag while we had 
external compactions and it would remain until we remove external dependencies 
and this compaction harden with fault testing.

Whether or not the feature is tagged as experimental seems orthogonal to the 
compaction implementation question (at least to me).

If I read the above correctly we are looking at 2.0 as a possible release for 
shipping this feature? I suggest we communicate the feature status as 
experimental for the whole release line, i.e. until 2.1, like what we have done 
with the cell security features in the 0.98 line. 

> HBase MOB
> ---------
>
>                 Key: HBASE-11339
>                 URL: https://issues.apache.org/jira/browse/HBASE-11339
>             Project: HBase
>          Issue Type: Umbrella
>          Components: regionserver, Scanners
>            Reporter: Jingcheng Du
>            Assignee: Jingcheng Du
>         Attachments: HBase MOB Design-v2.pdf, HBase MOB Design-v3.pdf, HBase 
> MOB Design-v4.pdf, HBase MOB Design.pdf, MOB user guide.docx, MOB user 
> guide_v2.docx, hbase-11339-in-dev.patch
>
>
>   It's quite useful to save the medium binary data like images, documents 
> into Apache HBase. Unfortunately directly saving the binary MOB(medium 
> object) to HBase leads to a worse performance since the frequent split and 
> compaction.
>   In this design, the MOB data are stored in an more efficient way, which 
> keeps a high write/read performance and guarantees the data consistency in 
> Apache HBase.



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

Reply via email to