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:05:06 GMT


Thejas M Nair commented on HIVE-10502:

Note that gets packaged into beeline jar, so only if some user needs
to customize the logs for beeline, they need to be aware of it.

I haven't seen useful messages at INFO level from beeline, so having it at WARN level in beeline
seemed like a good option. is used by servers as well, so having INFO
as default for them seems to be appropriate.

Note that the logging returned from HS2 does not get controlled by the log4j settings of beeline.

Sure, you can make the log4j location configurable for beeline, if you think that is useful.
But is that really the case ?

> 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