You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/01/10 18:44:00 UTC

[jira] [Commented] (HBASE-23279) Switch default block encoding to ROW_INDEX_V1

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

Michael Stack commented on HBASE-23279:
---------------------------------------

How we doing here [~vjasani]? [~anoop.hbase] reminded me this was outstanding in his review of HBASE-21065. In my test runs enabling ROW_INDEX_V1 on hbase:meta, the TestGetClosestAtOrBefore fails (commented out here) and then the TestProcedurePriority fails too as it does for you here. What you thinking? I was going to dig in but asking here first.

> 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)