[
https://issues.apache.org/jira/browse/YARN-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857918#comment-13857918
]
Vinod Kumar Vavilapalli commented on YARN-1399:
-----------------------------------------------
One thing that just occurred to me. Tags or the source/group originally
proposed won't help the oozie case as described on YARN-1390. Or to be more
accurate, they make it unwieldy. Let's say oozie uses a tag "workflow_123_566"
for all apps in a workflow, any other application from any other user SHOULD
not set that tag. Or run the risk of getting killed by oozie. That seems like
unintended behavior. To avoid it, we'll need to depend on oozie to not kill as
a privileged user.
Further, I could make any other user's application-search cumbersome by reusing
his/her tags for my own applications. Seems like the tag-search should be
linked to and limited by some other entity like user - search for apps matching
a tag for a given user/queue etc.
> 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)
