You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Michael Bieniosek <mi...@powerset.com> on 2007/08/16 23:54:03 UTC
binary backwards-incompatibility for 0.14.0
I've noticed a strange linking problem upgrading from previous hadoop
versions: the elimination of the JobClient(Configuration) constructor that
is backwards-compatible for source, but not for binaries. That is to say, I
built my job jar with hadoop-0.12.3; when I upgrade I have to do a full
rebuild (otherwise I get a nasty linking error) but don't have to change the
source.
-Michael
On 8/15/07 2:52 PM, "Doug Cutting" <cu...@apache.org> wrote:
> I've created a candidate build for Hadoop 0.14.0.
>
> http://people.apache.org/~cutting/hadoop-0.14.0-candidate-0/
>
> Should we release this?
>
> Doug
Re: binary backwards-incompatibility for 0.14.0
Posted by Owen O'Malley <oo...@yahoo-inc.com>.
On Aug 16, 2007, at 3:02 PM, Michael Bieniosek wrote:
> Well, it's not really fixable unless we want to reinstate the
> JobClient(Configuration) constructor. I assume there's a reason
> someone
> removed it?
Yeah, sorry about that. I modified the signature, since it should be
a JobConf, but I should have left the old one deprecated.
-- Owen
Re: binary backwards-incompatibility for 0.14.0
Posted by Michael Bieniosek <mi...@powerset.com>.
Well, it's not really fixable unless we want to reinstate the
JobClient(Configuration) constructor. I assume there's a reason someone
removed it?
We should just be aware that removing overloaded functions is not binary
backwards compatible, and try to minimize these sorts of API changes in the
future...
-Michael
On 8/16/07 2:58 PM, "Doug Cutting" <cu...@apache.org> wrote:
> This doesn't sound like a show-stopper to me. Does it to others?
>
> Doug
>
> Michael Bieniosek wrote:
>> I've noticed a strange linking problem upgrading from previous hadoop
>> versions: the elimination of the JobClient(Configuration) constructor that
>> is backwards-compatible for source, but not for binaries. That is to say, I
>> built my job jar with hadoop-0.12.3; when I upgrade I have to do a full
>> rebuild (otherwise I get a nasty linking error) but don't have to change the
>> source.
>>
>> -Michael
>>
>> On 8/15/07 2:52 PM, "Doug Cutting" <cu...@apache.org> wrote:
>>
>>> I've created a candidate build for Hadoop 0.14.0.
>>>
>>> http://people.apache.org/~cutting/hadoop-0.14.0-candidate-0/
>>>
>>> Should we release this?
>>>
>>> Doug
>>
Re: binary backwards-incompatibility for 0.14.0
Posted by Doug Cutting <cu...@apache.org>.
This doesn't sound like a show-stopper to me. Does it to others?
Doug
Michael Bieniosek wrote:
> I've noticed a strange linking problem upgrading from previous hadoop
> versions: the elimination of the JobClient(Configuration) constructor that
> is backwards-compatible for source, but not for binaries. That is to say, I
> built my job jar with hadoop-0.12.3; when I upgrade I have to do a full
> rebuild (otherwise I get a nasty linking error) but don't have to change the
> source.
>
> -Michael
>
> On 8/15/07 2:52 PM, "Doug Cutting" <cu...@apache.org> wrote:
>
>> I've created a candidate build for Hadoop 0.14.0.
>>
>> http://people.apache.org/~cutting/hadoop-0.14.0-candidate-0/
>>
>> Should we release this?
>>
>> Doug
>