hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maryann Xue (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7949) Enable big content store in HBase
Date Fri, 08 Mar 2013 07:54:15 GMT

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

Maryann Xue commented on HBASE-7949:

yes, you've made a good point here. flush would happen more frequently and compactions for
the meta data family will involve more small storefiles. however,
1. this approach best guarantees consistency.
2. several large content records get flushed into one file in one process, which means more
efficient I/O usage.
3. meta data is very small compared to large content data. moreover, one minor compaction
can handle a bunch of small meta data storefiles.
> 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

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

View raw message