[
https://issues.apache.org/jira/browse/YARN-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818751#comment-13818751
]
Karthik Kambatla commented on YARN-1390:
----------------------------------------
[~vinodkv], thanks for the inputs.
bq. A Pig query is a pig query and jobs spawned for a Pig query should be of
type Pig.
Correct. For our immediate usecase that [~rkanter] described, this should
definitely be enough. Let me create an MR JIRA to make that pluggable.
However, what if the pig query is part of an Oozie workflow? We could set it to
the Oozie workflow/action id, and Pig/MR shouldn't override it. But then, if we
want to list the Pig jobs being run by a user, we ll end up missing this job.
> 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)
