saveVersion.sh doesn't work when svn copy is staged
---
Key: MAPREDUCE-2888
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2888
Project: Hadoop Map/Reduce
Issue Type: Bug
Compon
MR changes to match HADOOP-7524 (multiple RPC protocols)
Key: MAPREDUCE-2887
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2887
Project: Hadoop Map/Reduce
Issue Type: Improvemen
Fix Javadoc warnings in MapReduce.
--
Key: MAPREDUCE-2886
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2886
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Mahadev konar
As
[
https://issues.apache.org/jira/browse/MAPREDUCE-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved MAPREDUCE-2550.
--
Resolution: Fixed
Arun updated the incremental changes of the script in MAPREDUCE-2885. Re
mapred-config.sh doesn't look for $HADOOP_COMMON_HOME/libexec/hadoop-config.sh
--
Key: MAPREDUCE-2885
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2885
Project: Hadoop
Greetings, Tucu. I'd like very much to take you up on that.
DistCpV2's build is currently mavenized. (Apologies. I neglected to mention
that in this mail-thread.) Could I please bother you to review the pom? As the
patch stands now, DistCpV2 needs building separately.
Grazie,
Mithun
_
And I'll be more than happy to review it from the Mavenization perspective.
Thxs.
Alejandro
On Fri, Aug 26, 2011 at 9:47 AM, Alejandro Abdelnur wrote:
> Please, don't add more Mavenization work on us (eventually I want to go
> back to coding)
>
> Given that Hadoop is already Mavenized, the patc
Please, don't add more Mavenization work on us (eventually I want to go back
to coding)
Given that Hadoop is already Mavenized, the patch should be Mavenized.
What will have to be done extra (besides Mavenizing distcp) is to create a
hadoop-tools module at root level and within it a hadoop-distcp
Agree with Mithun and Robert. DistCp and Tools restructuring are separate
tasks. Since DistCp code is ready to be committed, it need not wait for the
Tools separation from MR/HDFS.
I would say it can go into contrib as the patch is now, and when the tools
restructuring happens it would be just a
On Friday, August 26, 2011, Amareshwari Sri Ramadasu
wrote:
> Agree. It should be separate maven module (and patch puts it as separate
maven module now). And top level for hadoop tools is nice to have, but it
becomes hard to maintain until patch automation tests run the tests under
tools. Currentl
I agree with Mithun. They are related but this goes beyond distcpv2 and should
not block distcpv2 from going in. It would be very nice, however, to get the
layout settled soon so that we all know where to find something when we want to
work on it.
Also +1 for Alejandro's I also prefer to keep
Praveen,
The mapreduce modules still don't use the -Pdist -Dtar options to create the
TAR, please refer to the 'hadoop-mapreduce-project/INSTALL' notes for
details.
Thanks.
Alejandro
On Fri, Aug 26, 2011 at 5:13 AM, Praveen Sripati
wrote:
> Hi,
>
> I got the code from SVN for the branch-0.23 a
Would it be acceptable if retooling of tools/ were taken up separately? It
sounds to me like this might be a distinct (albeit related) task.
Mithun
From: Giridharan Kesavan
To: mapreduce-dev@hadoop.apache.org
Sent: Friday, August 26, 2011 12:04 PM
Subject: Re:
Hi,
I got the code from SVN for the branch-0.23 and ran the mvn command
svn co http://svn.apache.org/repos/asf/hadoop/common/branches/branch-0.23/
mvn clean install package -Pdist -Dtar -DskipTests
There were no errors. But, the hadoop-mapreduce-0.23.0-SNAPSHOT-all.tar.gz
file is not created.
p
[
https://issues.apache.org/jira/browse/MAPREDUCE-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Prakash reopened MAPREDUCE-2550:
-
Commit 103374ed71a22d614e77e79ac816fc72fbf93463 (Revision 161793) on branch-0.23
mapred-c
15 matches
Mail list logo