[
https://issues.apache.org/jira/browse/BIGTOP-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shaposhnik updated BIGTOP-734:
------------------------------------
Fix Version/s: 0.5.0
> Proposed fixes to Hive logging configuration
> --------------------------------------------
>
> Key: BIGTOP-734
> URL: https://issues.apache.org/jira/browse/BIGTOP-734
> Project: Bigtop
> Issue Type: Bug
> Reporter: Sean Mackrory
> Fix For: 0.5.0
>
> Attachments: BIGTOP-734.patch.1
>
>
> A few changes are needed to make Hive's logging work better.
> * The default configuration files have been renamed to have a .template
> suffix, but at least the log4j configuration files should lose the suffix so
> they can actually be used as the default configuration.
> * The HADOOP_OPTS variable needs to be set for all daemons, not just
> hive-server (otherwise logs get put in /tmp).
> * The HADOOP_OPTS variable should also specify hive.log.file so that the
> daemons have their own place and don't push junk into the hive.log file.
> * HIVE-3505 will, in the next Hive release, allow us to override the default
> logging threshold and make security audit messages from the metastore show up
> in the logs by default.
--
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