I believe these JIRAs should address those issues:
https://issues.apache.org/jira/browse/HADOOP-7563
https://issues.apache.org/jira/browse/HDFS-2277
--
Aaron T. Myers
Software Engineer, Cloudera
On Mon, Aug 22, 2011 at 1:16 PM, Thomas Graves wrote:
> What is the expected way to run from the t
What is the expected way to run from the tarballs?
It seems if I just untar them so they are in their separate directories (
hadoop-common-0.23.0-SNAPSHOT/, hadoop-hdfs-0.23.0-SNAPSHOT/,
hadoop-mapreduce-1.0-SNAPSHOT/), setup the ENV vars for HADOOP_COMMON_HOME,
HADOOP_HDFS_HOME, etc.. It won't ru
Nice job! Built right out of the box. Thanks for the instructions, very clear
and concise.
-Original Message-
From: Tom White [mailto:t...@cloudera.com]
Sent: Friday, August 19, 2011 12:56 PM
To: hdfs-dev@hadoop.apache.org
Cc: mapreduce-...@hadoop.apache.org
Subject: Re: Mavenizing the
Cos,
Thanks for catching that, I've missed that AOP was being used for 2
different things.
Alejandro
On Fri, Aug 19, 2011 at 11:37 AM, Konstantin Boudnik wrote:
> Right, Common has the tracking for AOP FI tests. There's Herrior work
> (system
> cluster tests) which is separate from FI although
Right, Common has the tracking for AOP FI tests. There's Herrior work (system
cluster tests) which is separate from FI although is using the same
technology.
My point was that HDFS ticket doesn't have any traces of it which makes me
wonder if it has been removed or else. I see your point and I'll
Hey Cos,
Given the size of the Mavenization work we broke into several pieces and we
are working them incrementally.
Because of that some disruption is happening to some parts of the build and
components.
There is a JIRA open for the AOP stuff (
https://issues.apache.org/jira/browse/HADOOP-7481)
I see that the whole AOP stuff has been taken out along with Herriot work.
I don't see any discussion about this on the JIRA. Neither I don't see any
tickets created to track the effort (but a subtask for FI tests in
HADOOP-7412).
Any reason we are missing a big chunk of validation infrastructure
HDFS-2096 is now committed to trunk. The instructions for building
HDFS can be found in the top-level BUILDING.txt file.
I added a script to https://issues.apache.org/jira/browse/HADOOP-7500
to help with migrating HDFS patches to the new layout.
There are a few follow-up patches that need doing s
+1, thanks for helping out by waiting on MR-279 - much appreciated!
Arun
On Aug 18, 2011, at 11:30 AM, Tom White wrote:
> Now that MR-279 has been merged into trunk, I plan to commit the HDFS
> mavenization changes tomorrow (Friday) at 9am PDT.
>
> Cheers,
> Tom
>
> On Mon, Aug 15, 2011 at 1:2
Now that MR-279 has been merged into trunk, I plan to commit the HDFS
mavenization changes tomorrow (Friday) at 9am PDT.
Cheers,
Tom
On Mon, Aug 15, 2011 at 1:24 PM, Arun C Murthy wrote:
> Thanks Tom.
>
> I'm running the final set of tests with the 'MR-279 rebased on trunk' and
> should be done
Thanks Tom.
I'm running the final set of tests with the 'MR-279 rebased on trunk' and
should be done by tmrw.
Also, can you guys please ensure that secure HDFS works after mvn'ization?
thanks,
Arun
On Aug 13, 2011, at 9:39 PM, Tom White wrote:
> Hi Arun,
>
> I'm fine with that. When do you e
Hi Arun,
I'm fine with that. When do you expect to start the vote?
Cheers,
Tom
On Fri, Aug 12, 2011 at 11:41 PM, Arun C Murthy wrote:
> Hi Tom,
>
> Can I request you to wait on this commit until we merge MR-279? As Vinod
> pointed out in his mail to mapreduce-dev@ we are very close to getting
Hi Tom,
Can I request you to wait on this commit until we merge MR-279? As Vinod
pointed out in his mail to mapreduce-dev@ we are very close to getting the
merge done. We should call a vote asap. By holding off it the mvn patch it will
save us a bit of time - we spent at more than a couple of
13 matches
Mail list logo
