[
https://issues.apache.org/jira/browse/HIVE-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548025#comment-13548025
]
Hudson commented on HIVE-3505:
------------------------------
Integrated in Hive-trunk-hadoop2 #54 (See
[https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
HIVE-3505. log4j template has logging threshold that hides all audit logs
(Sean Mackrory via cws) (Revision 1390278)
Result = ABORTED
cws : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1390278
Files :
* /hive/trunk/common/src/java/conf/hive-log4j.properties
* /hive/trunk/ql/src/java/conf/hive-exec-log4j.properties
> 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
> Fix For: 0.10.0
>
> Attachments: HIVE-3505.patch.1, HIVE-3505.patch.2, HIVE-3505.patch.3,
> HIVE-3505.patch.4
>
>
> 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