You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Jeyassri Balachandran (JIRA)" <ji...@apache.org> on 2019/07/29 09:57:00 UTC
[jira] [Commented] (RANGER-2522) Ranger Policy APIs - need to have
more endpoints
[ https://issues.apache.org/jira/browse/RANGER-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895114#comment-16895114 ]
Jeyassri Balachandran commented on RANGER-2522:
-----------------------------------------------
[/service/public/v2/api/policy?service=\{yarn}&resource:queue=\{queuename}|http://sl73caehmnc601:6080/service/public/v2/api/policy?service=ANAHDEV_yarn&resource:queue=test1]
Found it.
Closing the issue.
> Ranger Policy APIs - need to have more endpoints
> ------------------------------------------------
>
> Key: RANGER-2522
> URL: https://issues.apache.org/jira/browse/RANGER-2522
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: Jeyassri Balachandran
> Priority: Minor
>
> *+Improvements:+*
> We can make it better by exposing more API endpoints for Ranger Policies.
> We can have new APIs for getting/updating/deleting policy details by service - Yarn and filter by Queue Name instead of only doing it by policy id or policy name.
> +Eg+: *service/public/v2/api/service/YARN/queue/\{queueName}*
> +Reason+: From user perspective, we are also looking for queue names rather than policy id or policy name.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)