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

Craig Welch updated YARN-2505:
------------------------------
    Attachment: YARN-2505.3.patch

Attached is a preview patch - it is incomplete, lacking tests & not all planned 
interfaces are present yet, but a basic set is.  Couple minor changes wrt the 
plan a couple posts above - to keep consistency with the rest of the service 
interface I'm sticking with plural names everywhere (/nodes/, /node-labels/) & 
deferring (perhaps, permanently...) a couple of items which seem 
duplicative/purely for completeness but not really needed.


DONE

POST .../cluster/node-labels
(serialized data) adds multiple labels in an operation

GET .../cluster/node-labels
returns multiple labels as serialized data (all labels)

POST .../cluster/nodes/id/labels
(serialized data) adds multiple labels to a node in an operation

GET .../cluster/nodes/id/labels
returns serialized set of all labels for node

TODO NOW

DELETE .../cluster/node-labels/a
deletes an existing node label, "a"

DELETE .../cluster/nodes/id/labels/a
deletes label "a" from node "id"

PUT .../cluster/node-labels/a
creates a new node label, "a"

PUT .../cluster/nodes/id/labels/a
ads label "a" to node "id"

JUST DEFERRING FOR THE MOMENT - seems like a good idea, though

POST label to multiple nodes

DEFERRING - DUPLICATIVE

GET .../cluster/node-labels/a
return value indicates presence or absense of a

GET .../cluster/nodes/id/labels/a
indicates existance of label on node by return value

> Support get/add/remove/change labels in RM REST API
> ---------------------------------------------------
>
>                 Key: YARN-2505
>                 URL: https://issues.apache.org/jira/browse/YARN-2505
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Craig Welch
>         Attachments: YARN-2505.1.patch, YARN-2505.3.patch, YARN-2505.patch
>
>




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

Reply via email to