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 s
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
fu
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 binari
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
rebui
