On Mon, Jan 09, 2006 at 03:28:45PM -0800, Doug Cutting wrote: > > I'm still not clear why one might need a NullReporter.
To be more clear I should be a little more specific. I had to read in from a SequenceFile to interpret results of a string of MapReduce stages. Here's a simplified snippet. In this case I made a Reporter called nullreporter that just does nothing. SequenceFileInputFormat inputformat = new SequenceFileInputFormat(); RecordReader in = inputformat.getRecordReader(fshandle, split[i], logjob, nullreporter); I don't like having to specify a Reporter to getRecordReader(). Actually, as I've thought more about it, it's probably a bad idea to make a NullReporter class (although that might be better than nothing). Maybe a better solution would be simply to allow null to be passed in, but before calling setStatus(), check to make sure that it isn't null. Is that a good idea? -- Andrew McNabb http://www.mcnabbs.org/andrew/ PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868
signature.asc
Description: Digital signature
