From core-commits-return-8774-apmail-hadoop-core-commits-archive=hadoop.apache.org@hadoop.apache.org Tue May 19 17:23:14 2009
Return-Path:
Delivered-To: apmail-hadoop-core-commits-archive@www.apache.org
Received: (qmail 63918 invoked from network); 19 May 2009 17:23:13 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
by minotaur.apache.org with SMTP; 19 May 2009 17:23:13 -0000
Received: (qmail 20331 invoked by uid 500); 19 May 2009 17:23:13 -0000
Delivered-To: apmail-hadoop-core-commits-archive@hadoop.apache.org
Received: (qmail 20278 invoked by uid 500); 19 May 2009 17:23:13 -0000
Mailing-List: contact core-commits-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: core-dev@hadoop.apache.org
Delivered-To: mailing list core-commits@hadoop.apache.org
Received: (qmail 20269 invoked by uid 99); 19 May 2009 17:23:13 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2009 17:23:13 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.130] (HELO eos.apache.org) (140.211.11.130)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2009 17:23:10 +0000
Received: from eos.apache.org (localhost [127.0.0.1])
by eos.apache.org (Postfix) with ESMTP id 36103118BA
for ; Tue, 19 May 2009 17:22:49 +0000 (GMT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki
To: core-commits@hadoop.apache.org
Date: Tue, 19 May 2009 17:22:49 -0000
Message-ID: <20090519172249.1267.19711@eos.apache.org>
Subject: [Hadoop Wiki] Trivial Update of "Hive/HiveAws" by JoydeepSensarma
X-Virus-Checked: Checked by ClamAV on apache.org
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The following page has been changed by JoydeepSensarma:
http://wiki.apache.org/hadoop/Hive/HiveAws
------------------------------------------------------------------------------
We walk you through the choices involved here and show some practical case studies that contain detailed setup and configuration instructions.
== Running the Hive CLI ==
- Hive CLI environment is completely independent of Hadoop. The CLI takes in queries, compiles them into a plan consisting of map-reduce jobs and then submits them to a Hadoop Cluster. For this reason the CLI can be run from any node that has a Hive distribution, a Java Runtime Engine and that can connect to the Hadoop cluster. The Hive CLI also needs to access table metadata. By default this is persisted by Hive via an embedded Derby database into a folder named metastore_db on the local file system (however state can be persisted in any database - including remote mysql instances).
+ The CLI takes in Hive queries, compiles them into a plan (commonly, but not always, consisting of map-reduce jobs) and then submits them to a Hadoop Cluster. While it depends on Hadoop libraries for this purpose - it is otherwise relatively independent of the Hadoop cluster itself. For this reason the CLI can be run from any node that has a Hive distribution, a Hadoop distribution, a Java Runtime Engine. It can submit jobs to any compatible hadoop cluster (whose version matches that of the Hadoop libraries that Hive is using) that it can connect to. The Hive CLI also needs to access table metadata. By default this is persisted by Hive via an embedded Derby database into a folder named metastore_db on the local file system (however state can be persisted in any database - including remote mysql instances).
There are two choices on where to run the Hive CLI from: