hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jingcheng Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11339) HBase MOB
Date Thu, 19 Jun 2014 08:52:25 GMT

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

Jingcheng Du commented on HBASE-11339:
--------------------------------------

Hi [~jmhsieh], maybe I misunderstood your suggestion.

bq. I'm not convinced. The idea I'm suggesting is having a special lob log file that is written
once at write time that is essentially the lob store files in the doc, and put a reference
to it (file name, and offset) in the normal wal. This allows the lob to only be written once.
I don't see how this would be less efficient than an approach that must write the values out
at least twice.
You mean we have a new HLog implementation for the mob which write the mob file and wal separately,
right? And we still use the MemStore to save the mob data, right? I will draft the design
of the mob file and post it later. Thanks.

> HBase MOB
> ---------
>
>                 Key: HBASE-11339
>                 URL: https://issues.apache.org/jira/browse/HBASE-11339
>             Project: HBase
>          Issue Type: New Feature
>          Components: regionserver, Scanners
>            Reporter: Jingcheng Du
>            Assignee: Jingcheng Du
>         Attachments: HBase LOB Design.pdf
>
>
>   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.2#6252)

Mime
View raw message