[
https://issues.apache.org/jira/browse/HBASE-20649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20649:
--------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Release Note:
<!-- markdown -->
Users who have previously made use of prefix tree encoding can now check that
their existing HFiles no longer contain data that uses it with an additional
preupgrade check command.
```
hbase pre-upgrade validate-hfile
```
Please see the "HFile Content validation" section of the ref guide's coverage
of the pre-upgrade validator tool for usage details.
Status: Resolved (was: Patch Available)
nope, patch is great as is. Thanks for the reminder, I've pushed this to master
and branch-2 now.
Please feel free to edit the release note.
> Validate HFiles do not have PREFIX_TREE DataBlockEncoding
> ---------------------------------------------------------
>
> Key: HBASE-20649
> URL: https://issues.apache.org/jira/browse/HBASE-20649
> Project: HBase
> Issue Type: New Feature
> Components: Operability, tooling
> Reporter: Peter Somogyi
> Assignee: Balazs Meszaros
> Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-20649.master.001.patch,
> HBASE-20649.master.002.patch, HBASE-20649.master.003.patch,
> HBASE-20649.master.004.patch, HBASE-20649.master.005.patch,
> HBASE-20649.master.006.patch
>
>
> HBASE-20592 adds a tool to check column families on the cluster do not have
> PREFIX_TREE encoding.
> Since it is possible that DataBlockEncoding was already changed but HFiles
> are not rewritten yet we would need a tool that can verify the content of
> hfiles in the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
