[
https://issues.apache.org/jira/browse/HBASE-20592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491903#comment-16491903
]
Appy commented on HBASE-20592:
------------------------------
So in this patch, looks like it's meant to be run against 2.0 jars?
But isn't that a problem since 2.0 admin might be incompatible with 1.x
deployments?
I thought the initial approach was to have these tools such that they compile
against 1.x branch, and give them in a separate jar so that they can be run
before the upgrade is started. Has the approach changed?
> 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 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)
