Mailing-List: contact core-commits-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: core-commits@hadoop.apache.org
Date: Tue, 19 May 2009 17:14:17 -0000
Message-ID: <20090519171417.27923.61203@eos.apache.org>
Subject: [Hadoop Wiki] Update of "Hive/HiveAws/HivingS3nRemotely" by
 JoydeepSensarma

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/HivingS3nRemotely

------------------------------------------------------------------------------
   from lineitem where l_shipdate <= to_date('1998-12-01') group by l_returnflag, l_linestatus ; 
  }}}
  
- This launches one map-reduce job and on 10 nodes with default hadoop/hive settings - this took about 10 minutes. The results in this case are stored in HDFS and can be obtained by doing a {{{dfs -cat /tmp/tpcresults/1-2.sql/*}}} - either from bin/hadoop or from hive CLI. 
+ This launches one map-reduce job and on 10 nodes with default hadoop/hive settings - this took about 10 minutes. The results in this case are stored in HDFS and can be obtained by doing a {{{dfs -cat /tmp/tpcresults/1-2.sql/*}}} - either from bin/hadoop or from hive CLI. The query above differs from the TPCH query in skipping the order by clause - since it's not implemented by Hive currently.
  
  == Storing results back in S3 ==
  The results could also have been stored as a file in S3 directly, for example, we could alter the previous insert clause to read as: