Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 746A011431 for ; Tue, 23 Sep 2014 07:47:35 +0000 (UTC) Received: (qmail 34456 invoked by uid 500); 23 Sep 2014 07:47:35 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 34415 invoked by uid 500); 23 Sep 2014 07:47:35 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 34395 invoked by uid 99); 23 Sep 2014 07:47:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2014 07:47:35 +0000 Date: Tue, 23 Sep 2014 07:47:35 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-2505) [YARN-796] Support get/add/remove/change labels in RM REST API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144520#comment-14144520 ] Wangda Tan commented on YARN-2505: ---------------------------------- [~cwelch], Thanks for update. However, I just compared two patches, it seems the new one is double-sized of the old one. bq. -re rename all-nodes-to-lables to nodes-to-labels - done I found in the patch is still {code} + @GET + @Path("/labels/all-nodes-to-labels") {code} I guess you uploaded a wrong patch here. bq. -re node-filter I mis-understood the label filter before, it makes sense to me. Currently, REST will only return intersection set of labels on the nodes of the label filter passed in. But I think it may be also a valid use case when a user doesn't want to get whole set when intersection set is non-empty. For example, user want to query nodes contains label=GPU, and full sets of label returned can help user understand what else label contains in returned nodes. Are they in linux or windows platform, etc. So I propose to add an "do-intersection" (or some other name) parameter here, I think by default it can be either true/false, but user can have chance to set it. According to the comment: https://issues.apache.org/jira/browse/YARN-2494?focusedCommentId=14144501&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14144501. Do you think we need change add/remove labels to add/remove node labels? Wangda > [YARN-796] 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.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)