ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-20816) Create Ranger Hive Service during Hive Metastore restart
Date Fri, 21 Apr 2017 15:22:04 GMT


Hadoop QA commented on AMBARI-20816:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Console output:

This message is automatically generated.

> Create Ranger Hive Service during Hive Metastore restart
> --------------------------------------------------------
>                 Key: AMBARI-20816
>                 URL:
>             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|]
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 {{}} 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

View raw message