[
https://issues.apache.org/jira/browse/HBASE-20592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi updated HBASE-20592:
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.1
3.0.0
Release Note: PreUpgradeValidator tool with DataBlockEncoding validator
was added to verify cluster is upgradable to HBase 2.
Status: Resolved (was: Patch Available)
Pushed to branch-2.0 and up. Documentation part for upgrading.adoc was left out
for branch-2 since it does not have 'Upgrading from 1.x to 2.x' section. Thanks
for the reviews.
> 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: 3.0.0, 2.1.0, 2.0.1
>
> Attachments: HBASE-20592.master.001.patch,
> HBASE-20592.master.002.patch, HBASE-20592.master.003.patch,
> HBASE-20592.master.004.patch, HBASE-20592.master.005.patch,
> HBASE-20592.master.006.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)
