Return-Path: X-Original-To: apmail-hive-user-archive@www.apache.org Delivered-To: apmail-hive-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 03EBECE63 for ; Thu, 12 Jul 2012 18:53:38 +0000 (UTC) Received: (qmail 31032 invoked by uid 500); 12 Jul 2012 18:53:36 -0000 Delivered-To: apmail-hive-user-archive@hive.apache.org Received: (qmail 30844 invoked by uid 500); 12 Jul 2012 18:53:36 -0000 Mailing-List: contact user-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hive.apache.org Delivered-To: mailing list user@hive.apache.org Received: (qmail 30826 invoked by uid 99); 12 Jul 2012 18:53:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jul 2012 18:53:36 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of huy.pham.sc@gmail.com designates 209.85.213.176 as permitted sender) Received: from [209.85.213.176] (HELO mail-yx0-f176.google.com) (209.85.213.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jul 2012 18:53:30 +0000 Received: by yenl5 with SMTP id l5so3236710yen.35 for ; Thu, 12 Jul 2012 11:53:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=WyZMMeOKKBehXvXVb/wjzrDIK/n1L05OpsynYolMzPo=; b=Oda0bSfonPe+GUMg5xYJM/EtUvciJVULSgyGY/0t8bUmvKKyOOts4zl8/v2beUUv9A WfGiyFnEXb+Ssj0sJk34Fbb0KLSYAXOVI8wZ1IQxycaFd3eC+koJnF4QhDbVioBR/sh1 2nW/HSkdh7XEvvrja+IyvbdP3VBNxlKBevPklN9YyhRzlmIaQ9mIMmKdRtTbqWNLqArZ j6eBAuprHmd66GqhmX+hS3973KNc3FnNnmdGbIsHiOwRmc/2CM2SKuzYzX9Ged1MgERp EATiNP/UcgnFx22ZSyU8lecLg/OvO/NvYmYHSo5xpYhgjSB7W+V8ed1uj5H0saLWcoMG 8XTA== MIME-Version: 1.0 Received: by 10.60.8.200 with SMTP id t8mr19497134oea.7.1342119189588; Thu, 12 Jul 2012 11:53:09 -0700 (PDT) Received: by 10.76.80.233 with HTTP; Thu, 12 Jul 2012 11:53:09 -0700 (PDT) In-Reply-To: References: Date: Thu, 12 Jul 2012 11:53:09 -0700 Message-ID: Subject: Re: Output from HiveQL query From: VanHuy Pham To: user@hive.apache.org Content-Type: multipart/alternative; boundary=e89a8ff1ce4a8aabf804c4a67992 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff1ce4a8aabf804c4a67992 Content-Type: text/plain; charset=ISO-8859-1 The output can be printed out on terminal when you run it, or can be stored if you specify a location for it through the operator >. For example: /home/smith/bin/hive -f "file containing hive sql" > /home/smith/documents/output.txt On Thu, Jul 12, 2012 at 11:31 AM, Raihan Jamal wrote: > I have one question related to the output from the HiveQL query. Suppose I > did some HiveQL query and I will be getting some output back, so those > result set are getting stored somewhere in HDFS? If yes? > > 1) Then where they are getting stored and how can I access it?** > > 2) And is there any time limit on that meaning after this much > particular time it will be deleted?** > > > *Raihan Jamal* > > --e89a8ff1ce4a8aabf804c4a67992 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The output can be printed out on terminal when you run it, or can be stored= if you specify a location for it through the operator >.
For exampl= e:
--e89a8ff1ce4a8aabf804c4a67992--