Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 24 Apr 2012 06:05:46 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <334009491.8222.1335247546442.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <50998021.9172.1334915321029.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5842) Passing shell commands as an
 argument
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-5842:
------------------------------

We used to have it so you could pass a formatter class that the shell would use.  Default is console formatting.  We used to have an html output one which was useful when you could type in shell commands on ui and get results as an html page.  Another formatter would emit results per line so greppable.
                
> 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