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

Andrew Purtell commented on HBASE-7949:
---------------------------------------

bq. i suggest this issue not be committed into HBase trunk. instead we'd like 
to make the implementation a use case over HBase. and the only facility we need 
in HBase trunk is a pluggable flush process HBASE-8024

+1, agree with Maryann, let's consider making HBASE-8024 an Improvement issue 
and close this one, it lacks focus.
                
> 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

Reply via email to