[jira] [Updated] (MAPREDUCE-3154) Validate the Jobs Output Specification as the first statement in JobSubmitter.submitJobInternal(Job, Cluster) method

["Jane Chen (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jane Chen updated MAPREDUCE-3154:
---------------------------------

    Attachment: mapreduce-3377.patch
                err-after
                err-before
                out-after
                out-before

No new diff introduced by the proposed change on branch-1.

The reported issue does not occur on trunk.  Attached patch mapreduce-3377.patch includes only the unit test and is generated on trunk.

The other attachments shows that the added unit test passes after the proposed fix and no other diff is introduced.

out-before: stdout running "ant test" before the change.
err-before: stderr running "ant test" before the change.
out-after: stdout running "ant test" after the change.
err-after: stderr running "ant test" after the change.
                
> Validate the Jobs Output Specification as the first statement in JobSubmitter.submitJobInternal(Job, Cluster) method
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3154
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3154
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: client, mrv2
>    Affects Versions: 0.23.0, 0.24.0
>         Environment: mrv2
>            Reporter: Abhijit Suresh Shingate
>            Assignee: Abhijit Suresh Shingate
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-3154.patch, err-after, err-before, mapreduce-3377.patch, out-after, out-before
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Presently the output specification is validated after getting new JobId from ClientRMService, Copying the job jar, Configuration file, archives etc.
> Instead of that move following Job Output specification validation call to the begining of JobSubmitter.submitJobInternal(Job, Cluster) method.
> {code}
> checkSpecs(job);
> {code}
> This will avoid unnecessary work in case of invalid output specs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira