See https://builds.apache.org/job/Hadoop-Common-trunk/776/changes
Changes:
[sseth] Fixed incorrect jira in CHANGES.txt (YARN-716 to YARN-715)
[sseth] YARN-716. Fixed unit test failures - TestDistributedShell and
TestUnmanagedAMLauncher. Contributed by Vinod Kumar Vavilapalli.
[vinodkv]
+1 (non-binding)
On 05/17/2013 09:10 PM, Thomas Graves wrote:
Hello all,
We've had a few critical issues come up in 0.23.7 that I think warrants a
0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of
other issues that I want finished up and get in before we spin it. Those
Steve Loughran created HADOOP-9593:
--
Summary: stack trace printed at ERROR for all yarn clients without
hadoop.home set
Key: HADOOP-9593
URL: https://issues.apache.org/jira/browse/HADOOP-9593
(Resending - I think the first time I sent this out it got lost within all the
ByLaws voting)
Hi Folks
My name is Steve Watt and I am presently working on enabling glusterfs to be
used as a Hadoop FileSystem. Most of the work thus far has involved developing
a Hadoop FileSystem plugin for
[
https://issues.apache.org/jira/browse/HADOOP-7803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee resolved HADOOP-7803.
Resolution: Duplicate
The first put to a non-existing current directory doesn't work
I think we do a fairly good work maintaining a stable and public FileSystem
and FileContext API for third-party plugins to exist outside of Apache
Hadoop but still be able to work well across versions.
The question of test pops up though, specifically that of testing against
trunk to catch
See https://builds.apache.org/job/Hadoop-Common-trunk/777/changes
Changes:
[vinodkv] YARN-563. Add the concept of an application-type for each
application. Contributed by Mayank Bansal.
MAPREDUCE-5246. Specify application-type at the time of job submission after
YARN-563. Contributed by Mayank
Hi,
I'm working on HADOOP-9582https://issues.apache.org/jira/browse/HADOOP-9582
and I have a question about the current implementation in hadoop-common.
Here is a brief background about the bug : Basically if I give a non-exitent
file to hadoop fs –conf NONEXISTENT_FILE,
the current
[
https://issues.apache.org/jira/browse/HADOOP-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas reopened HADOOP-8562:
-
Reopening the issue for merging.
Enhancements to support Hadoop on
[
https://issues.apache.org/jira/browse/HADOOP-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HADOOP-8562.
-
Resolution: Fixed
Fix Version/s: (was: 3.0.0)
2.0.5-beta
Thanks for responding Harsh.
I agree. Hadoop Common does do a good job of maintaining a stable and public FS
and FS Context API. The pro for maintaining client libraries outside of Hadoop
Common is that the release owner of the library has much more autonomy and
agility in maintaining the
Alexander Veit created HADOOP-9595:
--
Summary: Error when error message should be printed to stderr
Key: HADOOP-9595
URL: https://issues.apache.org/jira/browse/HADOOP-9595
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved HADOOP-9546.
Resolution: Duplicate
Fixed by HADOOP-9593.
setsid exited with exit code
Trevor Lorimer created HADOOP-9596:
--
Summary: Add additional attributes to JMX beans
Key: HADOOP-9596
URL: https://issues.apache.org/jira/browse/HADOOP-9596
Project: Hadoop Common
Issue
You might try looking at what KosmoFS (KFS) did. They have some code in
org/apache/hadoop/fs which calls their own Java shim.
This way, the shim code in hadoop-common gets updated whenever FileSystem
changes, but there is no requirement to install KFS before building Hadoop.
You might also try
[
https://issues.apache.org/jira/browse/HADOOP-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junping Du reopened HADOOP-8469:
Backport this patch to branch-2
Make NetworkTopology class pluggable
From Bigtop perspective, Hadoop 2.0.4.1 is unblocked with regards to a Sqoop
2 blocker, and the voting can be started.
Anatoli
-- Forwarded message --
From: Konstantin Boudnik c...@apache.org
Date: Mon, May 20, 2013 at 9:03 PM
Subject: Re: Bugfix release 2.0.4.1
To:
Hi Stephen Watt,
I am a fresh developer trying to add a NFS-like FileSystem support for
Hadoop, and also have some confusion about the FileSystem Semantics.
Since I live in East Asia, I'd like to attend via Google Hangout if
possible.
Thanks.
+1 Kun Ling
yours,
Kun Ling
On
The quiet behavior sorta goes all the way back to the very first
import of Nutch into Apache Incubator:
http://svn.apache.org/viewvc?view=revisionrevision=155829 and seems
to deal with being relaxed about not finding added resources other
than required defaults. The behavior has almost been the
Jerry He created HADOOP-9597:
Summary: FileSystem open() API is not clear if
FileNotFoundException is throw when the path does not exist
Key: HADOOP-9597
URL: https://issues.apache.org/jira/browse/HADOOP-9597
20 matches
Mail list logo
