[
https://issues.apache.org/jira/browse/RANGER-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264512#comment-14264512
]
Gautam Borad commented on RANGER-210:
-------------------------------------
Currently Ranger provides the following binaries to start/stop ranger :
{noformat}ranger-admin/ews/start-ranger-admin.sh
ranger-admin/ews/stop-ranger-admin.sh{noformat}
Ranger also provides init.d scripts to start/stop ranger:
{noformat}service ranger-admin start
service ranger-admin stop{noformat}
Now for telling the version should we have yet another binary
({{ranger-admin-version}})? OR do we provide it as part of init.d scripts so
user can do {{service ranger-admin version}} ( not seen this behavior much with
*nix services )
I would suggest we club the functionality of start/stop/version into a single
ranger-admin.sh and take command line argument to invoke the required
functionality. This will give us the following functionalities from single
script :
# ranger-admin.sh start
# ranger-admin.sh stop
# ranger-admin.sh restart
# ranger-admin.sh --version OR ranger-admin.sh version
Please let me know your thoughts.
> Ranger service should tell it's Software verison
> ------------------------------------------------
>
> Key: RANGER-210
> URL: https://issues.apache.org/jira/browse/RANGER-210
> Project: Ranger
> Issue Type: Bug
> Affects Versions: 0.5.0
> Environment: Ranger should tell software version
> Reporter: Ashish Singh
> Assignee: Ashish Singh
> Fix For: 0.5.0
>
>
> Ranger should have capability to store the build info and other version info
> at build time, and software should have capability to output the version info
> at runtime.
> Hadoop and other apache components has this feature.
> Hadoop Refence Files.......
> {code}
> hadoop-common-project/hadoop-common/src/main/bin/hadoop
> hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/VersionInfo.java
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
