Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The "Hive/LanguageManual/Cli" page has been changed by JohnSichi. http://wiki.apache.org/hadoop/Hive/LanguageManual/Cli?action=diff&rev1=9&rev2=10 -------------------------------------------------- -hiveconf x=y Use this to set hive/hadoop configuration variables. -e and -f cannot be specified together. In the absence of these options, interactive shell is started + + To see this usage help, run hive -h + }}} * Example of running Query from command line @@ -37, +40 @@ == Hive interactive Shell Command == - When $HIVE_HOME/bin/hive ran without any -e/-f option it goes to interactive shell mode. + When $HIVE_HOME/bin/hive is run without either -e/-f option it enters interactive shell mode. ||'''Command '''||'''Description'''|| @@ -62, +65 @@ }}} === Logging === - Hive uses log4j for logging. These logs are not emitted to the standard output by default but are instead captured to a log file specified by the Hive's log4j properties file. By default Hive will use `hive-log4j.default` in the `conf/` directory of the hive installation which writes out logs to `/tmp/<userid>/hive.log` and uses the `WARN` level. + Hive uses log4j for logging. These logs are not emitted to the standard output by default but are instead captured to a log file specified by Hive's log4j properties file. By default Hive will use `hive-log4j.default` in the `conf/` directory of the hive installation which writes out logs to `/tmp/<userid>/hive.log` and uses the `WARN` level. It is often desirable to emit the logs to the standard output and/or change the logging level for debugging purposes. These can be done from the command line as follows: {{{ @@ -73, +76 @@ === Hive Resources === - Hive can manage the addition of resources to a session where those resources are available at query execution time. Currently the only supported resource is the FILE type. Any locally accessible file can be added to the session. Once a file is added to a session, hive query can refer to this file by it's name (in map/reduce/transform clauses) and this file is available locally at execution time on the entire hadoop cluster. Hive uses Hadoop's Distributed Cache to distribute the added files to all the machines in the cluster at query execution time. + Hive can manage the addition of resources to a session where those resources need to be made available at query execution time. Currently the only supported resource is the FILE type. Any locally accessible file can be added to the session. Once a file is added to a session, hive query can refer to this file by its name (in map/reduce/transform clauses) and this file is available locally at execution time on the entire hadoop cluster. Hive uses Hadoop's Distributed Cache to distribute the added files to all the machines in the cluster at query execution time. Usage: {{{ @@ -91, +94 @@ hive> from networks a MAP a.networkid USING 'python tt.py' as nn where a.ds = '2009-01-04' limit 10; }}} - It is not neccessary to add files to the session if the files used in a transform script are available on all machines in the hadoop cluster using the same path name. For example: + It is not neccessary to add files to the session if the files used in a transform script are already available on all machines in the hadoop cluster using the same path name. For example: * ... MAP a.networkid USING 'wc -l' ...: here wc is an executable available on all machines * ... MAP a.networkid USING '/home/nfsserv1/hadoopscripts/tt.py' ...: here tt.py may be accessible via a nfs mount point that's configured identically on all the cluster nodes.
