[
https://issues.apache.org/jira/browse/HBASE-20649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540112#comment-16540112
]
Sean Busbey commented on HBASE-20649:
-------------------------------------
Yeah, the steps I listed are what I'd like to document for operators. Or maybe
a summary like e.g. "when the files look like they're in the archive directory
you should check for tables with references as a result of cloning and for
snapshots" with a pointer back here for the specific step-by-step of commands
to run.
I agree that automating more of determining what actions are needed to clean
things up for upgrade would be useful. I'd like to have it wait for follow-on
work since at the moment we're dealing with cleanup for what's long been an
"experimental" data block encoding and I know [~balazs.meszaros]'s time is
limited and this particular work has been going back and forth for ~a month.
> 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
> Reporter: Peter Somogyi
> Assignee: Balazs Meszaros
> Priority: Minor
> Fix For: 3.0.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-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)
