I've already ported all our custom jobs (they use sequencefiles) and i ported the DomainStatistics tool (NUTCH-1221) but all jobs using mapfileoutputformat cannot be ported on 0.20.x.
It is indeed different in a consistent way but it is tedious (as you said earlier). I want to work on porting but also work on other things that still use the old api and use it on production. This is why i'd love to use 0.21 because it allows easy migration. On Thursday 15 December 2011 13:18:35 Andrzej Bialecki wrote: > On 15/12/2011 13:13, Markus Jelsma wrote: > > hmm, i don't see how i can use the old mapred MapOutputFormat API with > > the new Job API. job.setOutputFormatClass(MapFileOutputFormat.class) > > expects an the mapreduce.lib.output.MapFileOutputFormat class and won't > > accept the old API. > > > > setOutputFormatClass(java.lang.Class<? extends > > org.apache.hadoop.mapreduce.OutputFormat>) in > > org.apache.hadoop.mapreduce.Job cannot be applied to > > (java.lang.Class<org.apache.hadoop.mapred.MapFileOutputFormat>) > > > > In short, i don't know how i can migrate jobs to the new API on 0.20.x > > without having MapFileOutputFormat present in the new API. Trying to set > > to old mapoutputformat > > Ah, no, that's now what I meant ... of course you need to change the > code to use the new api, and the new code will look quite different :) > my point was only that it is different in a consistent way, so after > you've ported one or two classes the other ones are easy to convert, too... > > I'm bogged with other work now, but I'll see if I can prepare an example > later today... -- Markus Jelsma - CTO - Openindex
