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

Hadoop QA commented on AMBARI-15628:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12796256/AMBARI-15628.1.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 3 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:red}-1 core tests{color}.  The test build failed in ambari-server 

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

This message is automatically generated.

> Ranger: update code for jdbc according to new logic
> ---------------------------------------------------
>
>                 Key: AMBARI-15628
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15628
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: ambari-2.4.0
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>            Priority: Critical
>             Fix For: ambari-2.4.0
>
>         Attachments: AMBARI-15628.1.patch, AMBARI-15628.patch
>
>
> After code changes from AMBARI-15390, need to update Ranger, Ranger Plugin 
> and Ranger KMS code to support real time name for jdbc jar.



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

Reply via email to