hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3154) Validate the Jobs Output Specification as the first statement in JobSubmitter.submitJobInternal(Job, Cluster) method
Date Mon, 10 Oct 2011 04:44:29 GMT

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

Hudson commented on MAPREDUCE-3154:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #1069 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1069/])
    MAPREDUCE-3154. Fix JobSubmitter to check for output specs before copying job submission
files to fail fast. Contributed by Abhijit Suresh Shingate.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180774
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/JobSubmitter.java

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

        

Mime
View raw message