ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qiang Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (RANGER-1614) Similar to RANGER-1575, the Ranger UserSync should also support the same new feature.
Date Fri, 26 May 2017 01:24:04 GMT

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

Qiang Zhang resolved RANGER-1614.
---------------------------------
    Resolution: Fixed

> Similar to RANGER-1575, the Ranger UserSync should also support the same new feature.
> -------------------------------------------------------------------------------------
>
>                 Key: RANGER-1614
>                 URL: https://issues.apache.org/jira/browse/RANGER-1614
>             Project: Ranger
>          Issue Type: New Feature
>          Components: usersync
>    Affects Versions: 1.0.0
>            Reporter: peng.jianhua
>            Assignee: peng.jianhua
>            Priority: Minor
>              Labels: patch
>             Fix For: 1.0.0
>
>         Attachments: 0001-RANGER-1614-Similar-to-RANGER-1575-the-Ranger-UserSy.patch
>
>
> Similar to RANGER-1575, the Ranger UserSync should also support the same new feature.
> Some users hope that the pid file of theUserSync can be unified management when they
integrate Ranger into the big data platform or business systems to uniform install and run
Ranger.
> We should support the need in the case of compatibility with existing logic. When running
ranger, users can set the pid file to meet their own needs.
> We will explicitly document this change in the next release.



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

Mime
View raw message