Don't bet on it. The Hadoop RPC is pretty brittle. Adding security is the classic way to break things, but there have been instances (I think, but cannot name off the tip of my tongue) of other surprises.
When using stock Hadoop, I just don't allow any mismatches. My life is full enough of surprises. I don't need more. <conflict-of-interest>For the record, MapR has a commitment to allow rolling upgrades/downgrades across a single point release difference. This implies wire level compatibility.</conflict-of-interest> On Fri, Jul 1, 2011 at 8:54 AM, Sean Owen <[email protected]> wrote: > Not within one branch though, right? > Though I do agree, it's best to keep your client/server versions > synced, and should not be hard here at all. Whatever your cluster is: > match it in your client. > > On Fri, Jul 1, 2011 at 4:51 PM, Ted Dunning <[email protected]> wrote: > > You have to watch out, however, because Hadoop wire format changes pretty > > often. > > > > On Fri, Jul 1, 2011 at 7:21 AM, Xiaobo Gu <[email protected]> > wrote: > > > >> I mean mahout using the higher version of Hadoop libraries connecting > >> to a lower version of Hadoop cluster. > >> > >> On Fri, Jul 1, 2011 at 8:42 PM, Sean Owen <[email protected]> wrote: > >> > Yes, it's still compatible. > >> > > >> > On Fri, Jul 1, 2011 at 1:35 PM, Xiaobo Gu <[email protected]> > >> wrote: > >> >> Hi, > >> >> > >> >> Since the trunk of Mahout has moved to Hadoop 0.20.203, can we still > >> >> let Mahout connect to a lower version of Hadoop backend, such as > >> >> 0.20.2? > >> >> > >> >> Regards, > >> >> > >> >> Xiaobo Gu > >> >> > >> > > >> > > >
