[
https://issues.apache.org/jira/browse/YARN-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832138#comment-13832138
]
Karthik Kambatla commented on YARN-1390:
----------------------------------------
Doing this by the way of tags seems reasonable to me. However, as [~zjshen]
mentioned, faster filtering/lookup based on tags requires additional work of
adding a map <String (tag), List<RMApp> (apps)> to store the apps corresponding
to a particular tag in the RM. I propose we split this up into subtasks, so we
can take care of the simple field-adding and filtering first and add the
optimizations later. Can continue this discussion on YARN-1399.
> Provide a way to capture source of an application to be queried through REST
> or Java Client APIs
> ------------------------------------------------------------------------------------------------
>
> Key: YARN-1390
> URL: https://issues.apache.org/jira/browse/YARN-1390
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: api
> Affects Versions: 2.2.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
>
> In addition to other fields like application-type (added in YARN-563), it is
> useful to have an applicationSource field to track the source of an
> application. The application source can be useful in (1) fetching only those
> applications a user is interested in, (2) potentially adding source-specific
> optimizations in the future.
> Examples of sources are: User-defined project names, Pig, Hive, Oozie, Sqoop
> etc.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
