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 0BFE810F86 for ; Fri, 3 Jan 2014 18:22:18 +0000 (UTC) Received: (qmail 36091 invoked by uid 500); 3 Jan 2014 18:21:53 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 36040 invoked by uid 500); 3 Jan 2014 18:21:52 -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 35765 invoked by uid 99); 3 Jan 2014 18:21:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jan 2014 18:21:52 +0000 Date: Fri, 3 Jan 2014 18:21:51 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1399) Allow users to annotate an application with multiple tags 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-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861740#comment-13861740 ] Vinod Kumar Vavilapalli commented on YARN-1399: ----------------------------------------------- bq. How about adding a field (enum - visibility - own, viewable, all) in GetApplicationsRequest to capture this, the default for this could be "own". Yes, that would be the way to do it. bq. Instead of adding another API for getApplications with the restricted default view, how about changing existing GetApplicationsRequest.newInstance() methods to set the visibility to ALL? That way, we wouldn't change the behavior. We could add newInstance methods to capture rest of the fields - currently, we don't have newInstance methods for user, queue, etc. +1 > Allow users to annotate an application with multiple tags > --------------------------------------------------------- > > Key: YARN-1399 > URL: https://issues.apache.org/jira/browse/YARN-1399 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: Zhijie Shen > Assignee: Zhijie Shen > > Nowadays, when submitting an application, users can fill the applicationType field to facilitate searching it later. IMHO, it's good to accept multiple tags to allow users to describe their applications in multiple aspects, including the application type. Then, searching by tags may be more efficient for users to reach their desired application collection. It's pretty much like the tag system of online photo/video/music and etc. -- This message was sent by Atlassian JIRA (v6.1.5#6160)