[ 
https://issues.apache.org/jira/browse/AMBARI-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar resolved AMBARI-20816.
--------------------------------------
    Resolution: Fixed

> Create Ranger Hive Service during Hive Metastore restart
> --------------------------------------------------------
>
>                 Key: AMBARI-20816
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20816
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.5.1
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>            Priority: Blocker
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20816.patch, AMBARI-20816-trunk.patch
>
>
> Need to create Ranger Hive service in Cluster1 having Hive Metastore + Ranger 
> Service. The Ranger Hive service created in Cluster1 will be used by Cluster2 
> having Ranger Hive Plugin enabled under Hive Server2. 
> *Solution:*
> Need service creation logic using Ranger REST API. The REST API 
> [code|https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions_v2.py#L101]
>  is already available for use.
> If {{ranger.service.config.param.enable.hive.metastore.lookup}} property 
> present in {{ranger-hive-plugin-properties}} with value {{true}} and Ranger 
> configurations are present in the cluster(Ranger installed in same cluster) 
> then only create Ranger Hive service.
> For installation via blueprint, two extra custom config parameters 
> {{ranger.service.config.param.enable.hive.metastore.lookup}} with value 
> {{true}} and {{ranger.service.config.param.hive.site.file.path}} with value 
> {{/etc/hive/conf/hive-site.xml}} are required to be provided in blueprint 
> under {{ranger-hive-plugin-properties}} config type.
> For installation via UI, need to add properties in custom section of 
> ranger-hive-plugin-properties under Hive Service config tab.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to