In HBase land we've pretty well discovered that we'll need to have the
same version of protobuf that the HDFS/Yarn/MR servers are running.
That is to say there are issues with ever having 2.4.x and 2.5.x on
the same class path.
Upgrading to 2.5.x would be great, as it brings some new classes we
could use. With that said HBase is getting pretty close to a rather
large release (0.96.0 aka The Singularity) so getting this in sooner
rather than later would be great. If we could get this into 2.1.0 it
would be great as that would allow us to have a pretty easy story to
users with regards to protobuf version.
On Thu, Aug 8, 2013 at 8:18 AM, Kihwal Lee <[EMAIL PROTECTED]> wrote:
> Sorry to hijack the thread but, I also wanted to mention Avro. See HADOOP-9672.
> The version we are using has memory leak and inefficiency issues. We've seen users running into it.
> From: Tsuyoshi OZAWA <[EMAIL PROTECTED]>
> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Sent: Thursday, August 8, 2013 1:59 AM
> Subject: Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845
> About Hadoop, Harsh is dealing with this problem in HADOOP-9346.
> For more detail, please see the JIRA ticket:
> - Tsuyoshi
> On Thu, Aug 8, 2013 at 1:49 AM, Alejandro Abdelnur <[EMAIL PROTECTED]> wrote:
>> I' like to upgrade to protobuf 2.5.0 for the 2.1.0 release.
>> As mentioned in HADOOP-9845, Protobuf 2.5 has significant benefits to
>> justify the upgrade.
>> Doing the upgrade now, with the first beta, will make things easier for
>> downstream projects (like HBase) using protobuf and adopting Hadoop 2. If
>> we do the upgrade later, downstream projects will have to support 2
>> different versions and they my get in nasty waters due to classpath issues.
>> I've locally tested the patch in a pseudo deployment of 2.1.0-beta branch
>> and it works fine (something is broken in trunk in the RPC layer YARN-885).
>> Now, to do this it will require a few things:
>> * Make sure protobuf 2.5.0 is available in the jenkins box
>> * A follow up email to dev@ aliases indicating developers should install
>> locally protobuf 2.5.0