[
https://issues.apache.org/jira/browse/PHOENIX-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869423#comment-16869423
]
Hadoop QA commented on PHOENIX-5309:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12972435/PHOENIX-5309_v2.patch
against master branch at commit 493afe2c874e9e8f3fb52ab662ebcfa16f715ec2.
ATTACHMENT ID: 12972435
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation, build,
or dev patch that doesn't require tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2691//console
This message is automatically generated.
> Skip adding log4j and slf4j to phoenix-hive jar to avoid logging in
> hive-server2.err file than hiveserver2.log
> --------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-5309
> URL: https://issues.apache.org/jira/browse/PHOENIX-5309
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Priority: Major
> Attachments: PHOENIX-5309.patch, PHOENIX-5309_v2.patch
>
>
> Currently when there is mismatch in log4j versions in phoenix-hive jar and
> hive then possible logging of phoenix storage handler to hive-server2.err
> file than hiveserver2.log better way is to skip adding log4j and slf4j to
> phoeni-hive jar.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)