You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Maryann Xue (JIRA)" <ji...@apache.org> on 2013/03/07 04:36:15 UTC

[jira] [Updated] (HBASE-7949) Enable big content store in HBase

     [ https://issues.apache.org/jira/browse/HBASE-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maryann Xue updated HBASE-7949:
-------------------------------

    Attachment: HBase_LOB.pdf

At the recent hbase meetup, we just gave an introduction of an implementation for storing large objects.
The idea is to store the real content onto HDFS and let customized major compaction for this family handle the management work for these large contents.
And we need a customizable flush() process for this approach.
                
> Enable big content store in HBase
> ---------------------------------
>
>                 Key: HBASE-7949
>                 URL: https://issues.apache.org/jira/browse/HBASE-7949
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: chenning
>         Attachments: HBase_LOB.pdf
>
>
> Big content stored in hbase consumes a lot of system resource when region split or compaction operation happens.
> How HBase can be used to store big content along with some self descriptive meta-data. 
> The general idea is to add a new type of column family, and the content of this kind of column family doesn't participate the region split and compaction. An index(rowkey-location) is introduced in this new column family and the split and compaction are only applied to this index.

--
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