hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <>
Subject [jira] [Commented] (HIVE-10502) Cannot specify file location in Beeline
Date Thu, 30 Apr 2015 20:36:06 GMT


Thejas M Nair commented on HIVE-10502:

The idea was that almost all users would not want to get that noise from zookeeper code. WARN
level logging in beeline seems appropriate, but INFO level looks appropriate for HS2, metastore
etc. So a different beeline specific log file I feel is useful.
I am not against making log file name configurable, I am just trying to understand what you
expect users to point it to.

> Cannot specify file location in Beeline
> --------------------------------------------------------
>                 Key: HIVE-10502
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline
>    Affects Versions: 1.1.0
>            Reporter: Szehon Ho
>            Assignee: Chaoyu Tang
> 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:
> {noformat}
>   at org.apache.log4j.LogManager.<clinit>(
>   at org.slf4j.impl.Log4jLoggerFactory.getLogger(
>   at org.slf4j.LoggerFactory.getLogger(
>   at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(
>   at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(
>   at org.apache.commons.logging.LogFactory.getLog(
>   at org.apache.hadoop.util.VersionInfo.<clinit>(
> {noformat}
> It would be good to specify it, so it doesn't pick the first one in the classpath.

This message was sent by Atlassian JIRA

View raw message