Re: FileOutputCommiter behavior doubts

2012-05-23 Thread Harsh J
Thanks for following up here Subroto. Lets continue the discussion on the JIRA. On Wed, May 23, 2012 at 5:07 PM, Subroto wrote: > Thanks Harsh…. > Filed MAPREDUCE-4280 for the same…. > > > Cheers, > Subroto Sanyal > > On May 23, 2012, at 1:18 PM, Harsh J wrote: > > This is related: https://issues

Re: FileOutputCommiter behavior doubts

2012-05-23 Thread Subroto
Thanks Harsh…. Filed MAPREDUCE-4280 for the same…. Cheers, Subroto Sanyal On May 23, 2012, at 1:18 PM, Harsh J wrote: > This is related: https://issues.apache.org/jira/browse/MAPREDUCE-2493 > > But the real issue is LocalJobRunner does: > > OutputCommitter outputCommitter = job.getOutputCommi

Re: FileOutputCommiter behavior doubts

2012-05-23 Thread Harsh J
This is related: https://issues.apache.org/jira/browse/MAPREDUCE-2493 But the real issue is LocalJobRunner does: OutputCommitter outputCommitter = job.getOutputCommitter(); Which doesn't work with New API cause the OutputCommitter now comes from within the OutputFormat class. So hence you get th

FileOutputCommiter behavior doubts

2012-05-23 Thread Subroto
Hi, I have an implementation SampleFileOutputCommiter which extends org.apache.hadoop.mapred.FileOutputCommitter . The implementation has specific code to be executed during cleanupJob() execution. When the framework(LocalJobRunner) makes a call to commitJob(), the framework never takes care of