You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "peng.jianhua (JIRA)" <ji...@apache.org> on 2017/04/19 10:26:41 UTC

[jira] [Updated] (RANGER-1525) Some users hope that the execute programs and install configuration file of the Ranger Admin can be deployed separately when they integrate Ranger into the big data platform or business systems to uniform install Ranger.

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

peng.jianhua updated RANGER-1525:
---------------------------------
    Summary: Some users hope that the execute programs and install configuration file of the Ranger Admin can be deployed separately when they integrate Ranger into the big data platform or business systems to uniform install Ranger.  (was: Some users hope that the execute programs and configurations of the Ranger Admin can be deployed separately when they integrate Ranger into the big data platform or business systems.)

> Some users hope that the execute programs and install configuration file of the Ranger Admin can be deployed separately when they integrate Ranger into the big data platform or business systems to uniform install Ranger.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-1525
>                 URL: https://issues.apache.org/jira/browse/RANGER-1525
>             Project: Ranger
>          Issue Type: New Feature
>          Components: admin
>            Reporter: peng.jianhua
>            Assignee: peng.jianhua
>              Labels: features
>
> Some users hope that the execute programs and install configuration information of the Ranger Admin can be deployed separately when they integrate Ranger into the big data platform or business systems to install Ranger through the platform or systems. We should support the need in the case of compatibility with existing logic.
> Solution:
> 1. Users can set RANGER_ADMIN_CONF environment variable to meet their needs.
> 2. The program read configuration information from the RANGER_ADMIN_CONF path.
> 3. Users can re-plan programs and configurations when installing the Ranger Admin. Then they set  RANGER_ADMIN_CONF value as configuration path.



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