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.
This will avoid unnecessary work in case of invalid output specs.
- is related to
MAPREDUCE-2384 The job submitter should make sure to validate jobs before creation of necessary files