[
https://issues.apache.org/jira/browse/HBASE-11339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14356138#comment-14356138
]
Jingcheng Du commented on HBASE-11339:
--------------------------------------
Hi [~Wilm], if you want to enlarge the KeyValue size in your put, you could try
to change the conf("hbase.client.keyvalue.maxsize") used by the HTable, which
allows you have a larger KeyValue.
As Jon mentioned, LOBs in the current API will cause large memory allocations
that will stress the memory systems of both servers and the clients. You need
to pay attentions on this.
> HBase MOB
> ---------
>
> Key: HBASE-11339
> URL: https://issues.apache.org/jira/browse/HBASE-11339
> Project: HBase
> Issue Type: Umbrella
> Components: regionserver, Scanners
> Affects Versions: 2.0.0
> Reporter: Jingcheng Du
> Assignee: Jingcheng Du
> Fix For: hbase-11339
>
> Attachments: HBase MOB Design-v2.pdf, HBase MOB Design-v3.pdf, HBase
> MOB Design-v4.pdf, HBase MOB Design.pdf, MOB user guide.docx, MOB user
> guide_v2.docx, MOB user guide_v3.docx, MOB user guide_v4.docx, MOB user
> guide_v5.docx, hbase-11339-in-dev.patch, merge-150212.patch,
> merge.150212b.patch, merge.150212c.patch
>
>
> It's quite useful to save the medium binary data like images, documents
> into Apache HBase. Unfortunately directly saving the binary MOB(medium
> object) to HBase leads to a worse performance since the frequent split and
> compaction.
> In this design, the MOB data are stored in an more efficient way, which
> keeps a high write/read performance and guarantees the data consistency in
> Apache HBase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
