[
https://issues.apache.org/jira/browse/YARN-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815147#comment-13815147
]
Zhijie Shen commented on YARN-1390:
-----------------------------------
It sounds to me another way to categorize applications, but IMOH, it can still
make use of the "applicationType" field. Users can define the types based one
computation framework: mapreduce, tez, storm, mpi and etc, and also the ones
based on the *source*: pig, hive, oozie, sqoop and etc. It's just a different
opinions on the definition of the "applicationType".
Sometimes, users want to have both information, the computation framework and
the source. It sounds to me more like the requirement of sub-types:
||1st level||2nd level||
|hive|mapreduce|
| |tez|
|pig|mapreduce|
| |tez|
> Add applicationSource to ApplicationSubmissionContext and RMApp
> ---------------------------------------------------------------
>
> 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)
