...
/tmp/<user.name>/hive.log
Note: In local mode, the log file name is ".log" instead of "hive.log". This is a bug which will be fixed in a future release (see HIVE-5528).
If the user wishes – the logs can be emitted to the console by adding the arguments shown below:
...
When using local mode (using mapred.job.tracker=local), Hadoop/Hive execution logs are produced on the client machine itself. Starting v-0.6 – Hive uses the hive-exec-log4j.properties (falling back to hive-log4j.properties only if it's missing) to determine where these logs are delivered by default. The default configuration file produces one log file per query executed in local mode and stores it under /tmp/<user.name>. The intent of providing a separate configuration file is to enable administrators to centralize execution log capture if desired (on a NFS file server for example). Execution logs are invaluable for debugging run-time errors.
For information about WebHCat errors and logging, see Error Codes and Responses and Log Files in the WebHCat manual.
Error logs are very useful to debug problems. Please send them with any bugs (of which there are many!) to hive-dev@hadoop.apache.org.
...