[HIVE-12058] Change hive script to record errors when calling hbase fails

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.14.0, 1.1.0, 2.0.0
• Fix Version/s: 1.3.0, 2.0.0
• Component/s: Hive, HiveServer2
• Hadoop Flags: Reviewed
• Assignee: Yongzhi Chen
• Reporter: Yongzhi Chen
• Created: 07/Oct/15 20:44
• Updated: 30/Jan/17 23:43
• Resolved: 13/Oct/15 16:27

Description

By default hive will try to find out which jars need to be added to the classpath in order to run MR jobs against an HBase cluster, however if hbase can't be found or if hbase mapredcp fails, the hive script will fail silently and ignore some of the jars to be included into the. That makes very difficult to analyze the real problem.
Hive script should record the error not just simply redirect two hbase failures:
HBASE_BIN=$

{HBASE_BIN:-"$(which hbase 2>/dev/null)"}

$HBASE_BIN mapredcp 2>/dev/null

Issue Links

• breaks: HIVE-14288 Suppress 'which: no hbase' error message outputted from hive cli