Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 350E96AE1 for ; Tue, 7 Jun 2011 21:04:48 +0000 (UTC) Received: (qmail 21762 invoked by uid 500); 7 Jun 2011 21:04:46 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 21727 invoked by uid 500); 7 Jun 2011 21:04:46 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 21719 invoked by uid 99); 7 Jun 2011 21:04:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jun 2011 21:04:46 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.216.176 as permitted sender) Received: from [209.85.216.176] (HELO mail-qy0-f176.google.com) (209.85.216.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jun 2011 21:04:42 +0000 Received: by qyk30 with SMTP id 30so3407152qyk.14 for ; Tue, 07 Jun 2011 14:04:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=3UlsvWH5mVK6ID6vjrlXQdAc8IGs4ZbP1yt3TLbCtPM=; b=HR6rLmXp7XXu5KPOanmhwkBYc9bydS+hdJisiM5zbkFnRqeJtkhg9PTsnkqtrbrI9U un6SSkHW99e6FOXKArOItOmUmhOLZTAwKlLmUH3t6lOWJOGH7vIOZ+ZdQXS67AOMx93j GDVN3uVDMrCGH4x1dSNikSR87gP3CyUpyGBnw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=CzGOYBH8koYRXPPMOWZMDNYRzJHVmV5XCCTUUHiaaLl2avsmjRTulyk1w4EIatl0HE gTmu+gLa47wwul4UKh2zPIcYzCHz3guM7rirRrX7YvRmKFKAsIB4gvZaAE8K2EwdiGmP 6/24547NSaEJUG8g6/mjXmmAs3E4FVlFKCj5w= MIME-Version: 1.0 Received: by 10.224.70.195 with SMTP id e3mr3317981qaj.317.1307480661147; Tue, 07 Jun 2011 14:04:21 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.224.6.146 with HTTP; Tue, 7 Jun 2011 14:04:21 -0700 (PDT) In-Reply-To: References: Date: Tue, 7 Jun 2011 14:04:21 -0700 X-Google-Sender-Auth: TKFxftsDuQwsVW9mZGRL_xmLMyo Message-ID: Subject: Re: exporting from hbase as text (tsv) From: Stack To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dunno. Implication is that there is a MR cluster out there just sitting idle waiting on the occasional job of whimsy (if the data is 'big'). And, we'd have to make our load/dump at least as smart as the ? equivalent (fill in one from the list pig, hive, cascading, etc.)? Then why not just fire up the pig/hive/etc shells.... File an issue though lads. Above is just an opinion. St.Ack On Tue, Jun 7, 2011 at 11:35 AM, Jack Levin wrote: > Yes, shell could launch MR jobs; =A0I bet a lot of people will find this > feature very useful. > > -Jack > > On Tue, Jun 7, 2011 at 11:32 AM, Joey Echeverria wrot= e: >> I think Jack was suggesting that the shell would launch the MR jobs. >> >> -Joey >> On Jun 7, 2011 1:34 PM, "Stack" wrote: >>> On Tue, Jun 7, 2011 at 10:20 AM, Jack Levin wrote: >>>> That would be a real nice feature though, imagine going to the shell, >>>> and requesting a dump of your table. >>>> >>> >>> But it would only work for mickey mouse tables, no? If your >>> input/output is of any substantial size, wouldn't you want to MR it? >>> St.Ack >> >