[ 
https://issues.apache.org/jira/browse/AMBARI-16716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289650#comment-15289650
 ] 

Hadoop QA commented on AMBARI-16716:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12804676/AMBARI-16716.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6882//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6882//console

This message is automatically generated.

> Ambari copies jdbc driver jar into hadoop/lib and haoop-yarn/lib
> ----------------------------------------------------------------
>
>                 Key: AMBARI-16716
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16716
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16716.patch
>
>
> PROBLEM:
> Ambari copies the jdbc driver (be it mysql or oracle) into 
> /usr/hdp/xxx/hadoop/lib and /usr/hdp/xxx/hadoop-yarn/lib, this can cause 
> problem for hive and other components, as user updates the jar inside 
> /usr/hdp/xx/hive/lib, but those on the hadoop and yarn lib are also in the 
> classpath.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to