[
https://issues.apache.org/jira/browse/HIVE-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462221#comment-13462221
]
Sean Mackrory commented on HIVE-3505:
-------------------------------------
log4j.threshold and hive.root.logger specify two different levels. Should they
actually be the same, in reality or should only one be paramterized? Which
would be most intuitive considering how this file gets used?
> log4j template has logging threshold that hides all audit logs
> --------------------------------------------------------------
>
> Key: HIVE-3505
> URL: https://issues.apache.org/jira/browse/HIVE-3505
> Project: Hive
> Issue Type: Bug
> Components: Logging
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Attachments: HIVE-3505.patch.1, HIVE-3505.patch.2
>
>
> With the "template" for log4j configuration provided in the tarball, audit
> logging is hidden (it's logged as "INFO"). By making the log threshold a
> parameter, this information remains hidden when using the CLI (which is
> desired) but can be overridden when starting services to enable audit-logging.
> (This is primarily so that Hive is more functional out-of-the-box as
> installed by Apache Bigtop).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
