[
https://issues.apache.org/jira/browse/HBASE-23279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509115#comment-17509115
]
Bryan Beaudreault commented on HBASE-23279:
-------------------------------------------
Seems like this issue stalled a bit. For what it's worth, i've been perf
testing hbase1 vs hbase2 recently. In hbase1 we use PREFIX encoding (for
whatever historic reasons, we use that in like 400+ tables regardless of access
patterns). I noticed a perf regression with multigets between the 2 versions
and decided to give ROW_INDEX_V1 a shot due to Lars' blog post on the matter.
It's amazing how well it performs for this case, and I didnt see any regression
for scans. So I agree it might be nice to have as a default, if the other
blockers here can be overcome.
> Switch default block encoding to ROW_INDEX_V1
> ---------------------------------------------
>
> Key: HBASE-23279
> URL: https://issues.apache.org/jira/browse/HBASE-23279
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 3.0.0-alpha-1, 2.3.0
> Reporter: Lars Hofhansl
> Assignee: Viraj Jasani
> Priority: Minor
> Attachments: HBASE-23279.master.000.patch,
> HBASE-23279.master.001.patch, HBASE-23279.master.002.patch,
> HBASE-23279.master.003.patch, HBASE-23279.master.004.patch,
> HBASE-23279.master.005.patch
>
>
> Currently we set both block encoding and compression to NONE.
> ROW_INDEX_V1 has many advantages and (almost) no disadvantages (the hfiles
> are slightly larger about 3% or so). I think that would a better default than
> NONE.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
