[jira] [Commented] (AMBARI-20636) Allow users to add custom configs for Ranger service in all plugins

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-20636:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12861438/AMBARI-20636-trunk.patch
  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 tests.
                        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.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/11257//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11257//console

This message is automatically generated.

> Allow users to add custom configs for Ranger service in all plugins
> -------------------------------------------------------------------
>
>                 Key: AMBARI-20636
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20636
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.1
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20636.patch, AMBARI-20636-trunk.patch
>
>
> In order to help Ranger to communicate with Hive metastore (in cloud env) there is a need to allow users to add custom configs from Ambari, which needs to be added as part of Ranger service which gets created on Enabling plugins.
> This will be helpful for all plugins to define n-number of custom configs from Ambari.
> To add those configs, need to follow prefix "*ranger.service.config.param*" + config parameter.
> {panel:title=For blueprint based installs need to give those configs as below}
> {noformat}
> "ranger-<component>-plugin-properties": {
>   "ranger.service.config.param.configParameter1" : "vaule1",
>   "ranger.service.config.param.configParameter2" : "value2"
> }
> {noformat}
> {panel}
> {panel:title=For example in case of Hive}
> {noformat}
> "ranger-hive-plugin-properties": {
> "ranger.service.config.param.enable.hive.metastore.lookup": "false",
> "ranger.service.config.param.hive.site.file.path": "/etc/hive/conf/hive-site.xml"
> }
> {noformat}
> {panel}
> For UI based installs add those properties in custom section under ranger-<component>-plugin-properties. So that first restart of the component can take those value after enabling the plugin for the component.
> Note: This implies that if the service already existing in Ranger and user adds custom properties this will not be added to the existing service present in Ranger.



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