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 ZhengShao: http://wiki.apache.org/hadoop/Hive/GettingStarted ------------------------------------------------------------------------------ + Table of Contents + [[TableOfContents(4)]] + - DISCLAIMER: This is a prototype version of Hive and is NOT production + DISCLAIMER: This is a prototype version of Hive and is NOT production quality. However, + we are working hard to make Hive a production quality system. Hive has only been tested - quality. This is provided mainly as a way of illustrating the capabilities - of Hive and is provided as-is. However - we are working hard to make - Hive a production quality system. Hive has only been tested on unix(linux) - and mac systems using Java 1.6 for now - although it may very well work + on unix(linux) and mac systems using Java 1.6 for now - although it may very well work - on other similar platforms. It does not work on Cygwin right now. Most of + on other similar platforms. It does not work on Cygwin right now. Most of our testing has - our testing has been on Hadoop 0.17 - so we would advise running it against + been on Hadoop 0.17 - so we would advise running it against this version of hadoop - even - this version of hadoop - even though it may compile/work against other versions + though it may compile/work against other versions == Hive introduction videos From Cloudera == @@ -158, +159 @@ hive> DROP TABLE pokes; }}} - == Metadata Store == + === Metadata Store === Metadata is in an embedded Derby database whose disk storage location is determined by the hive configuration variable named javax.jdo.option.ConnectionURL. By default @@ -209, +210 @@ The two LOAD statements above load data into two different partitions of the table invites. Table invites must be created as partitioned by the key ds for this to succeed. - == Loading/Extracting data using Queries == + == SQL Operations == === Runtime configuration === * Hive queries are executed using map-reduce queries and, therefore, the behavior
