[ 
https://issues.apache.org/jira/browse/HBASE-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621212#comment-13621212
 ] 

stack commented on HBASE-7704:
------------------------------

[~himan...@cloudera.com] Thanks.

bq. It takes in a hbase directory path, and look for table directories 
(checking the presence of .tableinfo file). 

If it is a 'Tool', then, it will read Configurations off the CLASSPATH.  If so, 
it will have access to the hbase-default hbase.rootdir configuration. Given 
this, does it need to take a directory as input?  Also, since a Tool, you could 
override the property with -Dhbase.rootdir.

Or are you thinking that you should be able to point the tool at a subset of 
the hbase.rootdir content, say the a table directory?

That could be good to have (if not directory specified, use hbase.rootdir from 
the Configuration, else use what is passed).

Would suggest you Options parser that is in the HFilePRettyPrint.

Ok on NOT failing fast.  Lets go your route.  Going your route, seeing the 
paths to the v1 files will let operator know what tables need compacting.

Thanks boss.
                
> 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

Reply via email to