[
https://issues.apache.org/jira/browse/EAGLE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407097#comment-15407097
]
Hao Chen commented on EAGLE-408:
--------------------------------
We need define a generic and extensible framework to identify the normalize
what workflow scheduler applications are using. So the problem maybe much more
complex than only treat normalize name which in fact is the jobDefId.
In fact, as to any application, we should think about following attributions
* job definition id (so called normalized job name here)
* job execution id
* workflow definition id
* workflow execution id
* <more>
> Eagle-JPM job name normalize
> ----------------------------
>
> Key: EAGLE-408
> URL: https://issues.apache.org/jira/browse/EAGLE-408
> Project: Eagle
> Issue Type: New Feature
> Affects Versions: v0.5.0
> Reporter: wujinhu
> Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> In order to detect abnormal jobs and compare with the history of the same
> job, the hadoop users need to add a configure entry to the job config(like
> -Dealge.job.name="my job name") so that they can get the history information
> of the job with the same job name. In eagle jpm, we need read this configure
> entry from configuration, add to job entities and flush to hbase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
