hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5842) Passing shell commands as an argument
Date Fri, 20 Apr 2012 16:34:49 GMT

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

Jonathan Hsieh commented on HBASE-5842:
---------------------------------------

Harsh,  I would add that the output from the shell of that particular example is too clever
with formatting and ends up being cumbersome to use with standard unix parsing tools.

For that particular command, I've hacked the HFile tool do dump contents in an grep'able format.
 

Are you looking for that command in particular or are there more cases?

Maybe we should add a hbase-admin command that has shortcuts to utility methods like HLog,
HFile, and something like DumpMeta?


                
> Passing shell commands as an argument
> -------------------------------------
>
>                 Key: HBASE-5842
>                 URL: https://issues.apache.org/jira/browse/HBASE-5842
>             Project: HBase
>          Issue Type: Improvement
>          Components: shell
>    Affects Versions: 0.94.0
>            Reporter: Harsh J
>            Priority: Minor
>
> Many times we've required scans of .META. to analyze issues with the cluster we work
on, and to have the result in a file we can pass around we usually end up doing something
like:
> {{echo "scan '.META.'| hbase shell > meta-scan.txt}}
> This can rather be simplified as something like the following instead, with support for
a commands reading argument:
> {{hbase shell -c "scan '.META.'"}}
> [Note though: File reading is possible already, i.e. {{hbase shell file.hs}}, but then
thats two steps and we usually don't keep a file around for just a meta table scan.]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message