Return-Path: 
 <hbase-dev-return-677-apmail-hadoop-hbase-dev-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-hbase-dev-archive@locus.apache.org
Received: (qmail 99741 invoked from network); 19 Feb 2008 19:29:19 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 19 Feb 2008 19:29:19 -0000
Received: (qmail 79263 invoked by uid 500); 19 Feb 2008 19:29:13 -0000
Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org
Received: (qmail 79244 invoked by uid 500); 19 Feb 2008 19:29:13 -0000
Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hbase-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hbase-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hbase-dev@hadoop.apache.org>
List-Id: <hbase-dev.hadoop.apache.org>
Reply-To: hbase-dev@hadoop.apache.org
Delivered-To: mailing list hbase-dev@hadoop.apache.org
Received: (qmail 79190 invoked by uid 99); 19 Feb 2008 19:29:12 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Feb 2008 11:29:12 -0800
X-ASF-Spam-Status: No, hits=-1999.0 required=10.0
	tests=ALL_TRUSTED,FB_WORD1_END_DOLLAR
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Feb 2008 19:28:35 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id D6F46234C049
	for <hbase-dev@hadoop.apache.org>; Tue, 19 Feb 2008 11:28:43 -0800 (PST)
Message-ID: <1972446388.1203449323878.JavaMail.jira@brutus>
Date: Tue, 19 Feb 2008 11:28:43 -0800 (PST)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-447) Shell reads from stdin and writes to
 stdout
In-Reply-To: <31376204.1202965391038.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


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

stack commented on HBASE-447:
-----------------------------

Currently I can do this:

{code}
durruti:~/Documents/checkouts/hbase/trunk stack$ echo "create table 'x' ('x:');"| ./bin/hbase shellHQL, 0.2.0-dev version.Copyright (c) 2008 by udanax, licensed to Apache Software Foundation.Type 'help;' for usage.hql > create table 'x' ('x:');Creating table... Please wait.Table created successfully.hql > durruti:~/Documents/checkouts/hbase/trunk stack$
{code}

I can even do this and specify output format:

{code}
durruti:~/Documents/checkouts/hbase/trunk stack$ echo "show tables;"| ./bin/hbase shell --htmlHQL, 0.2.0-dev version.Copyright (c) 2008 by udanax, licensed to Apache Software Foundation.Type 'help;' for usage.hql > show tables;<table> <tr>  <th>Name  </th>  <th>Descriptor  </th> </tr> <tr>  <td>y  </td>  <td>name: y, families: {y:={name: y, max versions: 3, compression: NONE, in memory: false, block cache enabled: false, max length: 2147483647, bloom filter: none}}  </td> </tr> <tr>  <td>x  </td>  <td>name: x, families: {x:={name: x, max versions: 3, compression: NONE, in memory: false, block cache enabled: false, max length: 2147483647, bloom filter: none}}  </td> </tr></table>2 table(s) in set. (0.55 sec)hql > 
{code}

Should this issue be resolved as invalid?

> Shell reads from stdin and writes to stdout
> -------------------------------------------
>
>                 Key: HBASE-447
>                 URL: https://issues.apache.org/jira/browse/HBASE-447
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: hql
>            Reporter: Bryan Duxbury
>            Priority: Trivial
>
> Instead of HBASE-39, which would give you the ability to store queries in a file and execute them from the shell, we should give the shell the ability to read queries from standard input, execute the query, and then write the output to standard output. 
> The advantage of this approach is that in addition to being able to store queries in files, you can also script against the shell. This might mean schema creation during an installation wizard, or a shell script that queries a small number of rows, or whatever you can think of.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.