I made sure to write all the matrix and decomposer stuff in the old mapred.* hiearchy, so that is not on 0.20+ yet. But I don't know about the rest of it, I've seen lots of 0.18-based code as I dug around.
On Wed, May 26, 2010 at 1:10 AM, Sean Owen <[email protected]> wrote: > So, I converted to use the new APIs since Robin had mentioned that > most all the other code uses it. > > But I took a glance, and actually I don't see anything using the new > APIs at all except LDA and one FPM implementation. > > Are we talking about the same thing? > Basically we are talking about using nothing in org.apache.hadoop.mapred.* > > On Tue, May 25, 2010 at 4:33 PM, Robin Anil <[email protected]> wrote: > > +1 On moving forward and on using Abstract Job across the Codebase. > > > > > > On Tue, May 25, 2010 at 7:47 PM, Sean Owen <[email protected]> wrote: > > > >> Just to state what seems to be in progress -- looks like we are agreed > >> we should move to the new Hadoop APIs. Some code is already using it; > >> most of the part that isn't is the recommender which was due to some > >> strange bugs deep in Hadoop in prior versions. It's time to try it > >> again. I'm going to work on porting everything forward now. > >> > >> The other argument against this was that Amazon EMR runs 0.18.3. I > >> think Jeff already established that what we're doing has already > >> broken compatibility with 0.18.x. We can point those users to release > >> 0.3 and say they can try to back-port that code to 0.18.x > >> compatibility. But 0.4 onwards is for 0.20.x+ and you can run your own > >> cluster using AWS and hopefully EMR updates soon. > >> > >> Sean > >> > > >
