[
https://issues.apache.org/jira/browse/HBASE-20592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495577#comment-16495577
]
Mike Drob commented on HBASE-20592:
-----------------------------------
bq. +To change `PREFIX_TREE` encoding to supported one check
<<upgrade2.0.prefix-tree.removed,_prefix-tree_ encoding removed>>.
A few thoughts here -
Probably a good idea to link from the upgrade section back to the ops tools
sections so people reading the upgrade notes know what they need to do.
Also, that upgrade section doesn't actually describe how to change the
encoding, so need to either add the docs somewhere or point to a different
section.
> Create a tool to verify tables do not have prefix tree encoding
> ---------------------------------------------------------------
>
> Key: HBASE-20592
> URL: https://issues.apache.org/jira/browse/HBASE-20592
> Project: HBase
> Issue Type: New Feature
> Components: Operability, tooling
> Reporter: Peter Somogyi
> Assignee: Peter Somogyi
> Priority: Minor
> Fix For: 2.1.0
>
> Attachments: HBASE-20592.master.001.patch,
> HBASE-20592.master.002.patch, HBASE-20592.master.003.patch,
> HBASE-20592.master.004.patch
>
>
> HBase 2.0.0 removed PREFIX_TREE encoding so users need to modify data block
> encoding to something else before upgrading to HBase 2.0+. A tool would help
> users to verify that there are no tables left with PREFIX_TREE encoding.
> The tool needs to check the following:
> * There are no tables where DATA_BLOCK_ENCODING => 'PREFIX_TREE'
> * -Check existing hfiles that none of them have PREFIX_TREE encoding (in
> case table description is changed but hfiles were not rewritten)-
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
