[
https://issues.apache.org/jira/browse/HIVE-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623029#comment-13623029
]
Hudson commented on HIVE-3428:
------------------------------
Integrated in Hive-trunk-hadoop2 #138 (See
[https://builds.apache.org/job/Hive-trunk-hadoop2/138/])
HIVE-3428 : Fix log4j configuration errors when running hive on hadoop23
(Gunther Hagleitner via Ashutosh Chauhan) (Revision 1450645)
Result = FAILURE
hashutosh :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1450645
Files :
* /hive/trunk/common/src/java/conf/hive-log4j.properties
* /hive/trunk/data/conf/hive-log4j.properties
* /hive/trunk/pdk/scripts/conf/log4j.properties
* /hive/trunk/ql/src/java/conf/hive-exec-log4j.properties
* /hive/trunk/shims/ivy.xml
*
/hive/trunk/shims/src/common/java/org/apache/hadoop/hive/shims/HiveEventCounter.java
* /hive/trunk/shims/src/common/java/org/apache/hadoop/hive/shims/ShimLoader.java
> Fix log4j configuration errors when running hive on hadoop23
> ------------------------------------------------------------
>
> Key: HIVE-3428
> URL: https://issues.apache.org/jira/browse/HIVE-3428
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Zhenxiao Luo
> Assignee: Gunther Hagleitner
> Fix For: 0.11.0
>
> Attachments: HIVE-3428.1.D8805.patch, HIVE-3428.1.patch.txt,
> HIVE-3428.2.patch.txt, HIVE-3428.3.patch.txt, HIVE-3428.4.patch.txt,
> HIVE-3428.5.patch.txt, HIVE-3428.6.patch.txt,
> HIVE-3428_SHIM_EVENT_COUNTER.patch
>
>
> There are log4j configuration errors when running hive on hadoop23, some of
> them may fail testcases, since the following log4j error message could
> printed to console, or to output file, which diffs from the expected output:
> [junit] < log4j:ERROR Could not find value for key log4j.appender.NullAppender
> [junit] < log4j:ERROR Could not instantiate appender named "NullAppender".
> [junit] < 12/09/04 11:34:42 WARN conf.HiveConf: hive-site.xml not found on
> CLASSPATH
--
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
