You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Zhao, Qingwen (JIRA)" <ji...@apache.org> on 2016/10/08 06:37:20 UTC

[jira] [Commented] (EAGLE-408) Eagle-JPM job name normalize

    [ https://issues.apache.org/jira/browse/EAGLE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15557374#comment-15557374 ] 

Zhao, Qingwen commented on EAGLE-408:
-------------------------------------

Added jobDefId & jobExeId in the job definition for both running and historic jobs

jobDefId: a job definition id regardless of the job execution
jobExeId: a job execution id, similar to jobId 

> 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)