[
https://issues.apache.org/jira/browse/HBASE-20592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496605#comment-16496605
]
Mike Drob commented on HBASE-20592:
-----------------------------------
+1 on the patch.
One more thing to consider, however, is that maybe instead of being a new
separate command, this should be a subcommand under something like {{bin/hbase
pre-upgrade}}? I'm taking the big picture here between this, HBASE-20656, and
maybe others as we discover them.
So this would become {{bin/hbase pre-upgrade -validateDBE}} and probably we
would have an option to run all checks, and we could get better help into the
hands of the operators via the tool instead of pointing them at the ref-guide.
Thoughts? Maybe we can consolidate tools in a separate JIRA if you would rather
see this committed now.
> 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-20592.master.005.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)
