You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Carter Shanklin (JIRA)" <ji...@apache.org> on 2016/02/10 04:41:18 UTC
[jira] [Commented] (HIVE-12237) Use slf4j as logging facade
[ https://issues.apache.org/jira/browse/HIVE-12237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140253#comment-15140253 ]
Carter Shanklin commented on HIVE-12237:
----------------------------------------
The docs do need an update as I've found, when I follow the old style of hive --service hiveserver2 --hiveconf hive.root.logger=DEBUG,console on a Hive 2 build I get
{code}
2016-02-09 22:20:58,104 main ERROR Unable to locate appender DEBUG,console for logger
2016-02-09 22:20:58,106 main ERROR Unable to locate appender DEBUG,console for logger JPOX.Query
2016-02-09 22:20:58,107 main ERROR Unable to locate appender DEBUG,console for logger JPOX.General
2016-02-09 22:20:58,107 main ERROR Unable to locate appender DEBUG,console for logger JPOX.Enhancer
2016-02-09 22:20:58,108 main ERROR Unable to locate appender DEBUG,console for logger JPOX.Metadata
2016-02-09 22:20:58,108 main ERROR Unable to locate appender DEBUG,console for logger JPOX.Datastore
2016-02-09 22:20:58,108 main ERROR Unable to locate appender DEBUG,console for logger JPOX.Plugin
2016-02-09 22:20:58,109 main ERROR Unable to locate appender DEBUG,console for logger DataNucleus
2016-02-09 22:20:58,109 main ERROR Unable to locate appender DEBUG,console for logger Datastore
2016-02-09 22:20:58,110 main ERROR Unable to locate appender DEBUG,console for logger org.apache.zookeeper.ClientCnxnSocketNIO
2016-02-09 22:20:58,110 main ERROR Unable to locate appender DEBUG,console for logger org.apache.zookeeper.server.NIOServerCnxn
2016-02-09 22:20:58,111 main ERROR Unable to locate appender DEBUG,console for logger Datastore.Schema
{code}
There was also this warning:
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
When I renamed the template file hive-log4j2.xml.template to hive-log4j2.xml this error doesn't go away. I needed to create a new file named log4j2.xml instead.
Even so, setting all the levels there to DEBUG I'm not seeing all the log messages I used to see on Hive 1. I see a bunch of messages when HS2 starts but then nothing.
So in any event it's worth a doc update, but it would be really unfortunate if I couldn't control logging from the command line anymore.
> Use slf4j as logging facade
> ---------------------------
>
> Key: HIVE-12237
> URL: https://issues.apache.org/jira/browse/HIVE-12237
> Project: Hive
> Issue Type: Task
> Components: Logging
> Affects Versions: 2.0.0
> Reporter: Ashutosh Chauhan
> Assignee: Ashutosh Chauhan
> Fix For: 2.0.0
>
> Attachments: HIVE-12237.1.patch, HIVE-12237.2.patch, HIVE-12237.3.patch, HIVE-12237.4.patch, HIVE-12237.5.patch, HIVE-12237.6.patch, HIVE-12237.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)