You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Gautam Borad (JIRA)" <ji...@apache.org> on 2016/03/07 09:16:40 UTC
[jira] [Updated] (AMBARI-14383) Add support for Ranger TagSync
process as a component under RANGER
[ https://issues.apache.org/jira/browse/AMBARI-14383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gautam Borad updated AMBARI-14383:
----------------------------------
Fix Version/s: (was: 2.3.0)
> 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.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)