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/LanguageManual/Cli ------------------------------------------------------------------------------ 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. 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: + {{{ - {{{ $HIVE_HOME/bin/hive -hiveconf hive.root.logger=INFO,console }}} + $HIVE_HOME/bin/hive -hiveconf hive.root.logger=INFO,console + }}} + `hive.root.logger` specifies the logging level as well as the log destination. Specifying `console` as the target sends the logs to the standard error (instead of the log file). === Hive Resources === @@ -90, +93 @@ 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: * ... 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 the tt.py may be accessible via a nfs mount point that's configured similarly on all the cluster nodes. + * ... 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.
