[jira] [Created] (HDFS-5088) Exception in thread "main" java.lang.ClassCastException:occurs when running java org.apache.hadoop.hdfs.tools.HDFSConcat

Leo created HDFS-5088: - Summary: Exception in thread "main" java.lang.ClassCastException:occurs when running java org.apache.hadoop.hdfs.tools.HDFSConcat Key: HDFS-5088 URL: https://issues.apache.org/jira/browse/HDFS-5088

Build failed in Jenkins: Hadoop-Hdfs-0.23-Build #697

See -- [...truncated 7673 lines...] [ERROR] symbol : class Parser [ERROR] location: package com.google.protobuf [ERROR]

Hadoop-Hdfs-0.23-Build - Build # 697 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/697/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 7866 lines...] [ERROR] location: class com.google.pro

Hadoop-Hdfs-trunk - Build # 1489 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1489/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 8912 lines...] [ERROR] symbol : class Parser [ERROR] loc

Build failed in Jenkins: Hadoop-Hdfs-trunk #1489

See -- [...truncated 8719 lines...] [ERROR]

Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845

Like I said protoc is upgraded from 2.4 to 2.5. 2.5 is in the default path. If we still need 2.4 I may have to install it. Let me know -Giri On Sat, Aug 10, 2013 at 7:01 AM, Alejandro Abdelnur wrote: > thanks giri, how do we set 2.4 or 2.5., what is the path to both so we can > use and env to s

Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845

Giri, first of all, thanks for installing protoc 2.5.0. I didn't know we were installing them as the only version and not driven by env/path settings. Now we have a bit of a problem, precommit builds are broken because of mismatch of protoc (2.5.0) and protobuf JAR( 2.4.1). We have to options:

Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845

I can take care of re-installing 2.4 and installing 2.5 in a different location. This would fix 2.0 branch builds as well. Thoughts? -Giri On Mon, Aug 12, 2013 at 11:37 AM, Alejandro Abdelnur wrote: > Giri, > > first of all, thanks for installing protoc 2.5.0. > > I didn't know we were installi

Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845

About to commit HADOOP-9845 to trunk, in 5 mins. This will make trunk use protoc 2.5.0. thx On Mon, Aug 12, 2013 at 11:47 AM, Giridharan Kesavan < gkesa...@hortonworks.com> wrote: > I can take care of re-installing 2.4 and installing 2.5 in a different > location. This would fix 2.0 branch buil

Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845

I've just committed HADOOP-9845 to trunk (only trunk at the moment). To build trunk now you need protoc 2.5.0 (the build will fail with a warning if you don't have it). We'd propagate this to the 2 branches once the precommit build is back to normal and see things are OK. Thanks. On Mon, Aug 1

Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845

Ok. After installing protobuf 2.5.0 I can compile trunk. But now I cannot compile Hadoop-2 branches. None of them. So if I switch between branches I need to reinstall protobuf? Is there a consensus about going towards protobuf 2.5.0 upgrade in ALL versions? I did not get definite impression there

Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845

shooting to get it i n for 2.1.0. at moment is in trunk till the nightly finishes. then we'll decide in the mean time, you can have multiple versions installed in diff dirs and set the right one in the path thx Alejandro (phone typing) On Aug 12, 2013, at 17:47, Konstantin Shvachko wrote:

[jira] [Created] (HDFS-5089) When a LayoutVersion support SNAPSHOT, it must support FSIMAGE_NAME_OPTIMIZATION.

Tsz Wo (Nicholas), SZE created HDFS-5089: Summary: When a LayoutVersion support SNAPSHOT, it must support FSIMAGE_NAME_OPTIMIZATION. Key: HDFS-5089 URL: https://issues.apache.org/jira/browse/HDFS-5089

[UPDATE] Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845

Jenkins is running a full test run on trunk using protoc 2.5.0. https://builds.apache.org/job/Hadoop-trunk/480 And it seems go be going just fine. If everything looks OK, I'm planing to backport HADOOP-9845 to the 2.1.0-beta branch midday PST tomorrow. This will normalize all builds failures d