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

Hadoop QA commented on AMBARI-14383:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12797508/AMBARI-14383.3.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 2 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/6279//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6279//console

This message is automatically generated.

> Add support for Ranger TagSync process as a component under RANGER
> ------------------------------------------------------------------
>
>                 Key: AMBARI-14383
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14383
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-14383.1.patch, AMBARI-14383.2.patch, 
> AMBARI-14383.3.patch, AMBARI-14383.patch
>
>
> Ranger TagSync is a separate service that will be responsible for 
> synchronizing the tags from Apache Atlas into Apache Ranger (db).
> This jira will track changes required to install/configure TagSync from 
> Ambari.
> * Add Ranger TagSync component under existing RANGER service. 
> * The component will be a master component
> * Ability to start/stop the component independently of Ranger Admin.
> * Ability to install the component on any host of the cluster
> * Support should be available only from HDP 2.3
> * Any other changes required in Ambari stack to support such component



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

Reply via email to