This started out as something and ended up as something else altogether.
In any case, I think you should give a fresh heads up outside this thread.
There are a bunch of commits and merges happening into branch-2 and thus 2.0.5,
so it'll be safe to have an explicit hold-off/all-clear signaling.
See https://builds.apache.org/job/Hadoop-Common-trunk/785/changes
Changes:
[cdouglas] MAPREDUCE-5176. Add annotation for tagging tasks as responsive to
preemption. Contributed by Carlo Curino, cdouglas
[szetszwo] Move snapshot JIRAs to 2.0.5 section in CHANGES.txt.
[sseth] MAPREDUCE-5286.
On 30 May 2013 22:14, Adam Kawa kawa.a...@gmail.com wrote:
Hi,
When uploading new content (and information about my company), I got the
exception
Sorry, can not save page because rubbelloselotto.de is not allowed in
this wiki.
How could I solve it?
Kind regards,
Adam
the word lotto
[
https://issues.apache.org/jira/browse/HADOOP-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junping Du reopened HADOOP-8470:
Reopen this JIRA for backport to branch-2.
Implementation of 4-layer subclass of
On Thu, May 30, 2013 at 10:50 PM, Konstantin Boudnik c...@apache.org wrote:
Thanks Alejandro,
that's what my plan for the morning. Thanks for putting together the
check-list - would be easier for me not to miss anything. I am aiming to have
the bits out by noon or so. Appreciate the help!
Gopal V created HADOOP-9612:
---
Summary: HADOOP client IPC layer should differentiate between
interrupted threads and interrupts occurring during operations
Key: HADOOP-9612
URL:
On May 30, 2013, at 8:41 PM, Alejandro Abdelnur wrote:
Konstantin, Cos,
As we change from 2.0.4.1 to 2.0.5 you'll need to do the following
housekeeping as you work the new RC.
* rename the svn branch
* update the versions in the POMs
* update the CHANGES.txt in trunk, branch-2 and the
Thanks for the headstart Arun!
I will be sending a separate email to the *-dev@ lists outlining the plan and
the schedule of the changes, so we won't step on each other feet, like Vinod
expressed earlier.
Cos
On Fri, May 31, 2013 at 11:20AM, Arun C Murthy wrote:
On May 30, 2013, at 8:41 PM,
Guys,
I will be performing some changes wrt to moving 2.0.4.1 release candidate to
2.0.5 space. As outline below by Alejandro:
1. I will create new 2.0.5-alpha branch from the current head of 2.0.4-alpha
that contains 2.0.4.1 changes
2. consequently, set the artifacts version on the new branch
Hi Folks
I am grateful for the interest and to get so many responses (interested parties
that responded are on CC).
I like Steve Loughran's idea of having a few G+ hangouts first to get to some
consensus on how to organize the work as well as hear his thoughts about
leveraging the Hadoop
Cos, just to be clear, this is happening SAT JUN01 1PM-2PM PST, not now
(FRI MAY31 1PM PST). Correct?
Thx
On Fri, May 31, 2013 at 12:45 PM, Konstantin Boudnik c...@apache.org wrote:
Guys,
I will be performing some changes wrt to moving 2.0.4.1 release candidate
to
2.0.5 space. As outline
Indeed! The second part is happening on Saturday, JUN01 2013 1PM-2PM PST.
On Fri, May 31, 2013 at 01:01PM, Alejandro Abdelnur wrote:
Cos, just to be clear, this is happening SAT JUN01 1PM-2PM PST, not now
(FRI MAY31 1PM PST). Correct?
Thx
On Fri, May 31, 2013 at 12:45 PM, Konstantin
Timothy St. Clair created HADOOP-9613:
-
Summary: Updated jersey pom dependencies
Key: HADOOP-9613
URL: https://issues.apache.org/jira/browse/HADOOP-9613
Project: Hadoop Common
Issue
(forwarding to common-dev which is where this discussion about APIs should
go)
1. FileSystem API may add new methods from version to version. There's
some list operation that's gone in too.
2. I don't think there are any guarantees that we don't add new methods
to a base class -it's
On Fri, May 31, 2013 at 1:00 PM, Stephen Watt sw...@redhat.com wrote:
What is the protocol for organizing the logistics and collaborating? I am
loathe to flood common-dev with does this time work for you? emails from
the interested parties. Do we create a high level JIRA ticket and
All,
I have created a release candidate (rc0) for hadoop-2.0.5-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
discovered in the testing with BigTop 0.6.0 release candidate.
The RC is available at:
+1 (non-binding)
Thanks Cos.
Sangjin
On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik c...@apache.org wrote:
All,
I have created a release candidate (rc0) for hadoop-2.0.5-alpha that I
would
like to release.
This is a stabilization release that includes fixed for a couple a of
I am currently testing HBase 0.95 using 2.0.5-SNAPSHOT artifacts.
Would 2.1.0-SNAPSHOT maven artifacts be available after tomorrow's change ?
Thanks
On Fri, May 31, 2013 at 12:45 PM, Konstantin Boudnik c...@apache.org wrote:
Guys,
I will be performing some changes wrt to moving 2.0.4.1
Verified MD5 signature, built, configured pseudo cluster, run a couple of
sample jobs, tested HTTPFS.
Still, something seems odd.
The HDFS CHANGES.txt has the following entry under 2.0.5-alpha:
HDFS-4646. createNNProxyWithClientProtocol ignores configured timeout
value (Jagane Sundar via
Thanks for the hadoop-2.0.5-alpha RC0 Cos!
+1 (non-binding) in principle for a 2.0.5-alpha release.
Similar to Alejandro I see that:
/hadoop-2.0.5-alpha-src/hadoop-hdfs-project/README.txt (has 2.0.4 release
date missing):
Release 2.0.5-alpha - UNRELEASED
Release 2.0.4-alpha - UNRELEASED
Alejandro,
thanks for looking into this. Indeed - I missed the 2.0.5-alpha section in
YARN CHANGES.txt. Added now. As for HDFS-4646: apparently I didn't get into
to branch-2.0.4-alpha back then, although I distinctively remember doing this.
Let me pull it into 2.0.5-alpha and update CHANGES.txt
Ok, WRT HDFS-4646 - it is all legit and the code is in branch-2.0.4-alpha and
later. It has been committed as
r1465124
The reason it isn't normally visible because of the weird commit message:
svn merge -c1465121 from trunk
So, we good. I am done with the CHANGES.txt fixed that
All,
I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
discovered in the testing with BigTop 0.6.0 release candidate.
The RC is available at:
Thanks for fixing Cos.
http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc1/
looks good to me.
+1 (non-binding)
Thanks,
Joep
On Fri, May 31, 2013 at 8:25 PM, Konstantin Boudnik c...@apache.org wrote:
Ok, WRT HDFS-4646 - it is all legit and the code is in branch-2.0.4-alpha
and
later. It
+1 (non-binding)
Joep
On Fri, May 31, 2013 at 9:27 PM, Konstantin Boudnik c...@apache.org wrote:
All,
I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I
would
like to release.
This is a stabilization release that includes fixed for a couple a of
issues
discovered
25 matches
Mail list logo
