RE: [DISCUSS] Clarification on Compatibility Policy: Upgraded Client + Old Server

+1, I agree with your point Chris. It depends on the client application how they using the hdfs jars in their classpath. As implementation already supports the compatibility (through protobuf), No extra code changes required to support new Client + old server. I feel it will be good to explicit

Re: [DISCUSS] Clarification on Compatibility Policy: Upgraded Client + Old Server

I think this kind of compatibility issue still could surface for HDFS, particularly for custom applications (i.e. something not executed via "hadoop jar" on a cluster node, where the client classes ought to be injected into the classpath automatically). Running DistCP between 2 clusters of differe

Re: [DISCUSS] Clarification on Compatibility Policy: Upgraded Client + Old Server

It makes sense only for YARN today where we separated out the clients. HDFS is still a monolithic jar so this compatibility issue is kind of invalid there. +vinod On Mar 19, 2014, at 1:59 PM, Chris Nauroth wrote: > I'd like to discuss clarification of part of our compatibility policy. > Here i

[jira] [Resolved] (HADOOP-10184) Hadoop Common changes required to support HDFS ACLs.

[ https://issues.apache.org/jira/browse/HADOOP-10184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth resolved HADOOP-10184. Resolution: Fixed Fix Version/s: (was: 3.0.0) 2.4.0 Had

Re: [DISCUSS] Clarification on Compatibility Policy: Upgraded Client + Old Server

+1 on supporting new clients with old servers of the same major version, and updating the policy to capture that clearly. On Wed, Mar 19, 2014 at 1:59 PM, Chris Nauroth wrote: > I'd like to discuss clarification of part of our compatibility policy. > Here is a link to the compatibility document

[jira] [Resolved] (HADOOP-8921) ant build.xml in branch-1 ignores -Dcompile.native

[ https://issues.apache.org/jira/browse/HADOOP-8921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V resolved HADOOP-8921. - Resolution: Unresolved > ant build.xml in branch-1 ignores -Dcompile.native > --

[DISCUSS] Clarification on Compatibility Policy: Upgraded Client + Old Server

I'd like to discuss clarification of part of our compatibility policy. Here is a link to the compatibility documentation for release 2.3.0: http://hadoop.apache.org/docs/r2.3.0/hadoop-project-dist/hadoop-common/Compatibility.html#Wire_compatibility For convenience, here are the specific lines in

Re: Fixing MAPREDUCE-5748

Hey Hussein Thanks for picking MAPREDUCE-5748 up. Can you post the patch on the JIRA, and we can continue the conversation there? Thanks Karthik On Wed, Mar 19, 2014 at 12:55 PM, Hussein Baghdadi wrote: > Hi, > > I tried to fix MAPREDUCE-5748 > > What I did is to add another condition in addit

Re: Fixing MAPREDUCE-5748

Hi Karthik, I submitted the patch to https://issues.apache.org/jira/browse/MAPREDUCE-5748 I followed http://wiki.apache.org/hadoop/HowToContribute Thank you. Best, Hussein. On Wed, Mar 19, 2014 at 9:33 PM, Karthik Kambatla wrote: > Hey Hussein > > Thanks for picking MAPREDUCE-5748 up. Can y

Fixing MAPREDUCE-5748

Hi, I tried to fix MAPREDUCE-5748 What I did is to add another condition in addition to checking for nulls. I'm checking whether mapIds is empty or not if (mapIds == null || mapIds.size() == 0 || reduceQ == null || jobQ == null) I also created a unit test where 'map' param is missing. I'm not s

Re: Hadoop Build Server

OK do the following direct on mac osx mavericks 10.9.2 (i.e. without VMWare) - I svn checked out hadoop-trunk - installed xcode then installed protocol buffer - from hadood=trunk I invoked [mvn clean install] - got the following ... ... Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time ela

Build failed in Jenkins: Hadoop-Common-trunk #1074

See Changes: [zjshen] YARN-1690. Made DistributedShell send timeline entities+events. Contributed by Mayank Bansal. [cnauroth] HDFS-6099. HDFS file system limits not enforced on renames. Contributed by Chris Nauroth. [suresh] HD