-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41397/#review110558
-----------------------------------------------------------


I think until we know that hdp-select and conf-select will support this new 
component, that this component should be marked to not broadcast it's version.


ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
 (lines 108 - 113)
<https://reviews.apache.org/r/41397/#comment170493>

    This will fail if conf-select doesn't support ranger-tagsync (which I 
didn't find on my handful of deployments).



ambari-common/src/main/python/resource_management/libraries/functions/hdp_select.py
 (line 64)
<https://reviews.apache.org/r/41397/#comment170494>

    Not in hdp-select



ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py
 (line 71)
<https://reviews.apache.org/r/41397/#comment170496>

    Same as Alejandro's comment - does conf-select support this?


- Nate Cole


On Dec. 15, 2015, 11:46 a.m., Gautam Borad wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41397/
> -----------------------------------------------------------
> 
> (Updated Dec. 15, 2015, 11:46 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Madhan 
> Neethiraj, Mahadev Konar, Nate Cole, Sumit Mohanty, Selvamohan Neethiraj, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-14383
>     https://issues.apache.org/jira/browse/AMBARI-14383
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Ranger TagSync is a separate component that will be responsible for 
> synchronizing the tags from Apache Atlas into Apache Ranger (db).
> 
> 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
> 
> 
> Diffs
> -----
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
>  fd83c53 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/hdp_select.py
>  5628f33 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
>  b6e5ee9 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py
>  4f711c3 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
>  8de0d80 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-tagsync-site.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/metainfo.xml 
> 2fb8a9a 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  cf3afbe 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 
> cce20be 
> 
> Diff: https://reviews.apache.org/r/41397/diff/
> 
> 
> Testing
> -------
> 
> Installed Ranger on centos 6 and enabled Ranger TagSync module.
> 
> Tested minor upgrade from 2.3.x to 2.3.xx
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Reply via email to