[
https://issues.apache.org/jira/browse/AMBARI-20636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20636:
-------------------------------------
Description:
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.
was:
In order to help Ranger to communicate with Hive metastore (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.
> 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
>
>
> 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)
