[
https://issues.apache.org/jira/browse/HBASE-23279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020656#comment-17020656
]
Michael Stack commented on HBASE-23279:
---------------------------------------
FYI, GetClosest is a good test but with a bad name. It is named for a removed
method but the test was updated to use the new APIs. It runs a set of trying
lookups against the meta table. It fails because the ROW_INDEX_V1 encoder is
broken when it is set against hbase:meta. HBASE-23705 when it lands will fix
the problem.
What is in the way of landing this issue other than HBASE-23705 ? You still
have size concerns? You want it in hbase-2.3.0? Thanks.
> Switch default block encoding to ROW_INDEX_V1
> ---------------------------------------------
>
> Key: HBASE-23279
> URL: https://issues.apache.org/jira/browse/HBASE-23279
> Project: HBase
> Issue Type: Wish
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Lars Hofhansl
> Assignee: Viraj Jasani
> Priority: Minor
> Fix For: 3.0.0, 2.3.0
>
> Attachments: HBASE-23279.master.000.patch,
> HBASE-23279.master.001.patch, HBASE-23279.master.002.patch,
> HBASE-23279.master.003.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.3.4#803005)
