Ah ok, then that is probably the only base incompatibility you'll
encounter (it was captured by jdiff IIRC) and is almost the only
reason we've demanded jobs from 1.0 be recompiled before running on
2.0 (its a binary incompatible change made around ~0.21 time).
On Sat, Feb 9, 2013 at 11:23 AM, lohit <[EMAIL PROTECTED]> wrote:
> Thanks. What I am more interested is list of APIs where users have to
> change code.
> I know that on YARN I can run jobs which still use org.apache.hadoop.mapred
> But recently we hit a case where we had to change code for one case to
> start with.
> For example JobContext was class in 1.0 while Interface in 2.0. So, user
> has to change code.
> I was more interested in such cases (if it was documented)
> 2013/2/8 Harsh J <[EMAIL PROTECTED]>
>> Hey Lohit,
>> It may not be exactly in the form you're looking for, but take a look
>> at Dave's API Evolution page
>> http://dbeech.github.com/hadoop-api-evolution.html that presents a
>> matrix. Its psychedelic to look at, I know, but you asked for it ;)
>> We also generate jdiff reports as part of the regular maven build
>> (AFAIR), which may also be what you're looking for. From my experience
>> so far, its the behavior changes from 0.21+ thats biting users more
>> today than any API changes (there are far fewer API changes).
>> On Fri, Feb 8, 2013 at 11:51 PM, lohit <[EMAIL PROTECTED]> wrote:
>> > Hi Devs,
>> > Is there a documented list of API incompatibility between version 1.0 and
>> > version 2.0 of APIs.
>> > --
>> > Have a Nice Day!
>> > Lohit
>> Harsh J
> Have a Nice Day!