hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chenning (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7949) Enable big content store in HBase
Date Wed, 27 Feb 2013 05:36:13 GMT

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

chenning commented on HBASE-7949:
---------------------------------

I think the content itself should be stored in filesystem as file or the aggregated file,
Hbase stores a location or location/offset information. The application built on top of HBase
or HDFS can implement it too, however,the implementation in HBase level can simplify the application
and leverage some good mechanisms of HBase. 
                
> 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
>
> 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

Mime
View raw message