TestHDFSTrash failing on 22
---
Key: HADOOP-7663
URL: https://issues.apache.org/jira/browse/HADOOP-7663
Project: Hadoop Common
Issue Type: Bug
Components: test
Reporter: Mayank Bansal
[
https://issues.apache.org/jira/browse/HADOOP-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley reopened HADOOP-7633:
File log4j.properties was left out of the commit to trunk and v0.23 branches.
> log4j.properties shou
[
https://issues.apache.org/jira/browse/HADOOP-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-7633.
Resolution: Fixed
Committed to trunk and v0.23.
> log4j.properties should be added to the hadoop
[
https://issues.apache.org/jira/browse/HADOOP-7630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-7630.
Resolution: Fixed
Two items: First, this bug is marked for trunk/v0.23 as well as
security/v0.20.
logs servlet should use pathspec of /*
--
Key: HADOOP-7662
URL: https://issues.apache.org/jira/browse/HADOOP-7662
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: T
FileSystem.getCanonicalServiceName throws NPE for any file system uri that
doesn't have an authority.
-
Key: HADOOP-7661
URL: https://issues.apache.org/jira/browse
Shrinivas,
The MapOutputBuffer.compare() is the primary method for all Map-output
key comparisons (for the sorting done at map end).
Your job.getOutputKeyComparator() is the one utilized within that for
comparing all KV pairs as they are emitted out by the Mapper for
Reduce's-consumption (and fur
With JVM inlining enabled, profiles of Terasort run show more than 3% time
spent in MapTask$MapOutputBuffer.compare( ) method in each of the Map JVMs.
In this particular configuration there are 8 Map JVMs. So a big chunk of
time is spent in this particular method. With JVM inlining disabled,
java.n
Some more info, i attached the screenshot to know where exactly you need to
edit after opening the below link provided by Steve.
Regards,
Uma
- Original Message -
From: Steve Loughran
Date: Tuesday, September 20, 2011 10:21 pm
Subject: Re: Change Jira email address
To: common-dev@hadoop.
Thanks Seve, that works.
On Tue, Sep 20, 2011 at 9:48 AM, Steve Loughran wrote:
> On 20/09/11 17:24, J. Rottinghuis wrote:
>
>> Does anybody know how one changes the e-mail address associated with their
>> Jira account?
>> When logging in to Apache Jira I can change my password on the profile
>
On 20/09/11 17:24, J. Rottinghuis wrote:
Does anybody know how one changes the e-mail address associated with their
Jira account?
When logging in to Apache Jira I can change my password on the profile page,
but I do not see a link where to change the email address.
Thanks,
Joep
go to view pr
Does anybody know how one changes the e-mail address associated with their
Jira account?
When logging in to Apache Jira I can change my password on the profile page,
but I do not see a link where to change the email address.
Thanks,
Joep
Thanks Bobby and Alejandro for your inputs.
> > Please open a JIRA to follow up with this. Note that is not only in
> common
> > that code is generated, but in mapreduce as well. And there are
> different
> > things being generated, avro, protobuf, etc.
Filed a new JIRA for this issue
https://iss
Maven generated .classpath doesnot includes "target/generated-test-source/java"
as source directory.
Key: HADOOP-7660
URL: https://issues.apache.org/jira/browse/H
Sorry that was a different page I looked at before going to the JIRA.
It said that we can manually add in the target/generated-test-source/java
directory as a source directory with something like
target/generated-test-source/java/**/*.java
I have no idea if it will work, but it looked cleaner t
Bobby,
What is the POM change you are referring to?
Thanks.
Alejandro
On Tue, Sep 20, 2011 at 7:00 AM, Robert Evans wrote:
> This is a known issue with the eclipse maven mojo
>
> http://jira.codehaus.org/browse/MECLIPSE-37
>
> The JIRA also describes a workaround, add the generated tests dir
This is a known issue with the eclipse maven mojo
http://jira.codehaus.org/browse/MECLIPSE-37
The JIRA also describes a workaround, add the generated tests directory in the
eclipse config with a pom change, which I think would be better then trying to
move the phase where test code is generate
Laxman,
This is not an incorrect usage of maven phases, those generated Java classes
are test classes, thus is generation in the 'generate-test-sources' phase.
The problem seem to be that eclipse does not recognize the
target/generated-test-source/java directory as a source directory (for
example
Hi All,
I can see lot of compilation issues after setting up my development
environment using "mvn eclipse:eclipse".
All these compilation issues are resolved after adding
"target/generated-test-sources" as a source folder to the common project.
When verified the "pom.xml", it's noticed th
fs -getmerge isn't guaranteed to work well over non-HDFS filesystems
Key: HADOOP-7659
URL: https://issues.apache.org/jira/browse/HADOOP-7659
Project: Hadoop Common
Issue Ty
20 matches
Mail list logo
