[
https://issues.apache.org/jira/browse/YARN-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832039#comment-13832039
]
Karthik Kambatla commented on YARN-1390:
----------------------------------------
bq. but I am still not sure if having an applicationLineage field is a good
idea.
I agree that it will not be used in YARN or AHS, but I think is key metadata to
be associated with an application. This, IMO, is similar to appName which is
also not directly used by YARN, but is basic information corresponding to an
app.
bq. If it is an implementation question and we are looking at supporting some
form of tags, I believe a key-value map is the best approach. Tags can be
represented in the map.
Will <source: oozie-action-id> be an example of key-value pair in the map? If
yes, are the keys predefined or upto the user? Pre-defined keys won't really
help us capture everything users would want to tag the application with.
> 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)
