hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Subru Krishnan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4340) Add "list" API to reservation system
Date Wed, 02 Dec 2015 23:39:11 GMT

    [ https://issues.apache.org/jira/browse/YARN-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036873#comment-15036873
] 

Subru Krishnan commented on YARN-4340:
--------------------------------------

Thinking more about it, I am not sure we should have user in the interface. We should automatically
pick up user from context. If we want to allow user, then it should be an Admin API and not
a Client API IMHO. 

> Add "list" API to reservation system
> ------------------------------------
>
>                 Key: YARN-4340
>                 URL: https://issues.apache.org/jira/browse/YARN-4340
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, fairscheduler, resourcemanager
>            Reporter: Carlo Curino
>            Assignee: Sean Po
>         Attachments: YARN-4340.v1.patch, YARN-4340.v2.patch, YARN-4340.v3.patch, YARN-4340.v4.patch
>
>
> This JIRA tracks changes to the APIs of the reservation system, and enables 
> querying the reservation system on which reservation exists by "time-range, reservation-id,
username".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message