I didn't say that right. What I meant was: If I added Hadoop 2.2, 2.3, and 2.4 profiles, and in those profiles override the protobuf version... There should be no issue with that, correct? The default protobuf version would remove 2.4.x.
-- Lars ________________________________ From: Jean-Marc Spaggiari <[email protected]> To: dev <[email protected]> Sent: Wednesday, April 2, 2014 5:03 AM Subject: Re: protobuf version in 0.94 Hum, that means Hadoop 1.0.x and 1.2.x branches will fail... 2014-04-02 2:53 GMT-04:00 Esteban Gutierrez <[email protected]>: > For HBase itself is not a problem :) it compiles, but users running HBase > 0.94.x in clusters pre HADOOP-9845 they will hit issues during rolling > restarts specially if the 2.4.0 jar is present. For instance, that can > break MR jobs. > > esteban. > > > > > -- > Cloudera, Inc. > > > > On Tue, Apr 1, 2014 at 9:31 PM, lars hofhansl <[email protected]> wrote: > > > Is anybody aware of any reason why we wouldn't just update the protobuf > > version in 0.94 to 2.5.0? > > > > I know 2.5.0 is backward compatible with 2.4.0, but is the reverse true > as > > well? > > I.e. if we do not change any .proto files will 2.4.0 be able to decoded > > message encoded with 2.5.0? > > If yes, we should just upgrade. If not we can't upgrade since it would > > potentially break server-server compatibility and hence rolling upgrades. > > > > -- Lars >
