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

["Enis Soztutar (JIRA)" <ji...@apache.org>]

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

Enis Soztutar commented on HBASE-7949:
--------------------------------------

Thanks for working on this. I think this is an important problem, and will enable HBase for new use cases. However, I feel like we should fix the core issues that prevents this use case from stock HBase, rather than writing a fairly complex flush + compaction policy just for LOBs. I guess, you mentioned that with custom compaction policy, the problem is with region splits. Can you elaborate on that? There is also a problem because of lack of streaming RPC, but the issue is also there in your proposal. 
                
> 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