[
https://issues.apache.org/jira/browse/HBASE-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621187#comment-13621187
]
Himanshu Vashishtha commented on HBASE-7704:
--------------------------------------------
I have started working on this. I am using the approach of a java standalone
program (aka tool), which has an executor service. It takes in a hbase
directory path, and look for table directories (checking the presence of
.tableinfo file). Then, it dives in to the table directory and look for any v1
file, and list it out. I was not thinking to make it a failfast one, as it is
good to see all such files in one go (they may be in different region/tables)?
Yes, this should be done before user actually migrate. As we have removed all
v1 related code from 0.95, it can't compact on its own. Therefore, user will
run this script and check for the presence of any v1 file, and run compaction
on it.?
> migration tool that checks presence of HFile V1 files
> -----------------------------------------------------
>
> Key: HBASE-7704
> URL: https://issues.apache.org/jira/browse/HBASE-7704
> Project: HBase
> Issue Type: Task
> Reporter: Ted Yu
> Priority: Blocker
> Fix For: 0.95.1
>
>
> Below was Stack's comment from HBASE-7660:
> Regards the migration 'tool', or 'tool' to check for presence of v1 files, I
> imagine it as an addition to the hfile tool
> http://hbase.apache.org/book.html#hfile_tool2 The hfile tool already takes a
> bunch of args including printing out meta. We could add an option to print
> out version only – or return 1 if version 1 or some such – and then do a bit
> of code to just list all hfiles and run this script against each. Could MR it
> if too many files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
