[ https://issues.apache.org/jira/browse/OOZIE-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184501#comment-14184501 ]
Harsh J commented on OOZIE-2024: -------------------------------- Failing tests appear unrelated from what I could check in their sources. The change is just in the message, error code stays the same. > Confusing message when a job can't be looked up by JavaActionExecutor > --------------------------------------------------------------------- > > Key: OOZIE-2024 > URL: https://issues.apache.org/jira/browse/OOZIE-2024 > Project: Oozie > Issue Type: Improvement > Components: action > Affects Versions: 4.0.0 > Reporter: Harsh J > Assignee: Harsh J > Priority: Minor > Attachments: OOZIE-2024.patch, OOZIE-2024.patch, OOZIE-2024.patch > > > When you have issues where JT is missing job history or JHS is lacking it, > causing JavaActionExecutor to fail when its RunningJob is returned back as > null, it prints a very confusing message such as below, that can read instead > as "This is not the Job ID I was supposed to find" instead of what is meant > to be "I could not find this Job ID on the server": > {code} > "JA017: Unknown hadoop job [job_12048563533402_20232] associated with action > [1129661-1909061866638236-oozie-oozi-W@java-action]. Failing this action!” > {code} > What would instead be clearer is this: > {code} > "JA017: Could not lookup launched hadoop job ID [job_12048563533402_20232] > which was associated with action > [1129661-1909061866638236-oozie-oozi-W@java-action]. Failing this action!” > {code} > Patch attached, feel free to refine further during commit if the text is > unsatisfactory in parts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)