[HIVE-10502] Cannot specify log4j.properties file location in Beeline

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.1.0
• Component/s: Beeline
• Assignee: Chaoyu Tang
• Reporter: Szehon Ho
• Created: 27/Apr/15 18:50
• Updated: 29/Apr/16 12:55
• Resolved: 15/Oct/15 21:20

Description

In HiveCLI, HiveServer2, HMS, etc, the following is called early in the startup to initialize log4j logging: LogUtils.initHiveLog4j().

However, seems like this is not the case in Beeline, which also needs log4j like as follows:

  at org.apache.log4j.LogManager.<clinit>(LogManager.java:127)
  at org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:66)
  at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:270)
  at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:156)
  at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:132)
  at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:657)
  at org.apache.hadoop.util.VersionInfo.<clinit>(VersionInfo.java:37)

It would be good to specify it, so it doesn't pick the first one in the classpath.