Hello all,
I have posted a release candidate for Hadoop 1.0.0 at
    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/

Please download, evaluate, and vote on this list.
The artifacts will be posted to the maven repo shortly.
The vote will close at noon PST on Thursday 15 Dec.

It may be of interest that it is important to use an appropriate version of
Java.
I lost several days due to instabilities apparently in Oracle JDK 1.6.0_23,
which
caused about 30 junit test failures in contrib (streaming, schedulers, and
gridmix).
Switching to JDK 1.6.0_26 made the problems go away.

The release artifacts in this hadoop-1.0.0-rc2 were build with JDK 1.6.0_26.

Thank you,
--Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)

On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Hello all,
> I have posted a release candidate for Hadoop 1.0.0 at
>    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>
> Please download, evaluate, and vote on this list.

Pulled into Bigtop, built and running integrations tests today.

Quick question though: how come this one is not fixed?
     https://issues.apache.org/jira/browse/MAPREDUCE-3319
There's a patch posted, etc *and* it wasn't reproducible
in the branch. I'm confused.

Thanks,
Roman.

Hi Roman,
regarding MAPREDUCE-3319<https://issues.apache.org/jira/browse/MAPREDUCE-3319>
I'm
confused too.  Your comment in the bug as of 28/Nov/11 21:49 seems to
indicate that it is fixed, but clearly it wasn't fixed the same way as
Subroto's patch (which came in on Dec 6).

Anyway, I reviewed and committed Subroto's patch to branch-1.  If there is
a need to regenerate the RC for 1.0.0, I'll merge it to branch-1.0, but I
hope no one will think this is serious enough to be a cause to regenerate
the RC just for this patch.

BTW, the same change would be applicable to trunk, so I've left the bug
open.

--Matt

On Fri, Dec 9, 2011 at 2:47 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:

> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
> > Hello all,
> > I have posted a release candidate for Hadoop 1.0.0 at
> >    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
> >
> > Please download, evaluate, and vote on this list.
>
> Pulled into Bigtop, built and running integrations tests today.
>
> Quick question though: how come this one is not fixed?
>     https://issues.apache.org/jira/browse/MAPREDUCE-3319
> There's a patch posted, etc *and* it wasn't reproducible
> in the branch. I'm confused.
>
> Thanks,
> Roman.
>

On Fri, Dec 9, 2011 at 3:26 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Hi Roman,
> regarding MAPREDUCE-3319 I'm confused too.  Your comment in the bug as
> of 28/Nov/11 21:49 seems to indicate that it is fixed, but clearly it wasn't
> fixed the same way as Subroto's patch (which came in on Dec 6).

What is the tag corresponding to this RC?  The svn rev. where I couldn't
reproduce it is this: branch-1.0@1207581 not sure how it relates to the rev
from which the RC was cut. That's why I asked this question on a JIRA:
   https://issues.apache.org/jira/browse/MAPREDUCE-3319?focusedCommentId=13158818&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13158818

> Anyway, I reviewed and committed Subroto's patch to branch-1.  If there is a
> need to regenerate the RC for 1.0.0, I'll merge it to branch-1.0, but I hope
> no one will think this is serious enough to be a cause to regenerate the RC
> just for this patch.

It would be sad to see 1.0 with a bundled example that doesn't work out of
the box because of a trivial problem. There's only been one day of RC
out there and the fix seems very low risk. Given that, perhaps the
trade-off of wasting one day of potential testing of RC by a community
can be considered.

I can offer any help with regenerating the RC with patch applied that you
might need.

Thanks,
Roman.

Roman, the 1.0.0-rc2 is built from branch-1.0@1211738, which contains
c1207581.
Is the problem consistently reproducible in 1.0.0-rc2?  Perhaps you're
seeing
some intermittent behavior?

On Fri, Dec 9, 2011 at 3:57 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:

> On Fri, Dec 9, 2011 at 3:26 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
> > Hi Roman,
> > regarding MAPREDUCE-3319 I'm confused too.  Your comment in the bug as
> > of 28/Nov/11 21:49 seems to indicate that it is fixed, but clearly it
> wasn't
> > fixed the same way as Subroto's patch (which came in on Dec 6).
>
> What is the tag corresponding to this RC?  The svn rev. where I couldn't
> reproduce it is this: branch-1.0@1207581 not sure how it relates to the
> rev
> from which the RC was cut. That's why I asked this question on a JIRA:
>
> https://issues.apache.org/jira/browse/MAPREDUCE-3319?focusedCommentId=13158818&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13158818
>
> > Anyway, I reviewed and committed Subroto's patch to branch-1.  If there
> is a
> > need to regenerate the RC for 1.0.0, I'll merge it to branch-1.0, but I
> hope
> > no one will think this is serious enough to be a cause to regenerate the
> RC
> > just for this patch.
>
> It would be sad to see 1.0 with a bundled example that doesn't work out of
> the box because of a trivial problem. There's only been one day of RC
> out there and the fix seems very low risk. Given that, perhaps the
> trade-off of wasting one day of potential testing of RC by a community
> can be considered.
>
> I can offer any help with regenerating the RC with patch applied that you
> might need.
>
> Thanks,
> Roman.
>

On Fri, Dec 9, 2011 at 4:30 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Roman, the 1.0.0-rc2 is built from branch-1.0@1211738, which contains
> c1207581.

Thanks. This is useful to know. Wish I had that info earlier :-(

> Is the problem consistently reproducible in 1.0.0-rc2?  Perhaps you're
> seeing  some intermittent behavior?

Well, when I tried to reproduce it (and couldn't) I was running a
pseudo-distributed
setup on my latop. When I see the problem -- it is on a fully
distributed cluster
running off of Bigtop Jenkins:
    http://bigtop01.cloudera.org:8080/view/RCs/job/Bigtop-rc-smoketest/
This *may* have something to do with it.

Anyway, now that we have the patch that actually fixes the issue 100%, the
real question is -- whether we should apply it to RC.

Thanks,
Roman.

P.S. In the future I'll try to reproduce everything over @Bigtop jenkins so that
at least we have a "paper trail" of things. Running tests over there is
pretty cheap.

+Carl (the only person from Hive project I know ;-))

On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Hello all,
> I have posted a release candidate for Hadoop 1.0.0 at
>    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/

Ok, my test run is now past HBase (horray! that works).

That's the good news so far. The bad news is -- this release
is incompatible with hive:

$ hive
Hive requires Hadoop 0.20.x (x >= 1).
'hadoop version' returned:
Hadoop 1.0.0.2 Subversion -r Compiled by jenkins on Fri Dec 9 13:29:12 EST 2011

This is, of course, a minor, but a VERY annoying thing.

Thoughts on what to do?

Thanks,
Roman.

P.S. I wish the test run took less than half a day :-(

Hey Roman,

That problem is at Hive end. You can try out the patch at
https://issues.apache.org/jira/browse/HIVE-2631 to unblock your testing.

Thanks,
Ashutosh

On Fri, Dec 9, 2011 at 18:21, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:

> +Carl (the only person from Hive project I know ;-))
>
> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
> > Hello all,
> > I have posted a release candidate for Hadoop 1.0.0 at
> >    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>
> Ok, my test run is now past HBase (horray! that works).
>
> That's the good news so far. The bad news is -- this release
> is incompatible with hive:
>
> $ hive
> Hive requires Hadoop 0.20.x (x >= 1).
> 'hadoop version' returned:
> Hadoop 1.0.0.2 Subversion -r Compiled by jenkins on Fri Dec 9 13:29:12 EST
> 2011
>
> This is, of course, a minor, but a VERY annoying thing.
>
> Thoughts on what to do?
>
> Thanks,
> Roman.
>
> P.S. I wish the test run took less than half a day :-(
>

On Fri, Dec 9, 2011 at 6:29 PM, Ashutosh Chauhan <[EMAIL PROTECTED]> wrote:
> Hey Roman,
>
> That problem is at Hive end. You can try out the patch at
> https://issues.apache.org/jira/browse/HIVE-2631 to unblock your testing.

Sure. As I said -- the fix is pretty simple. However, releasing this
would break every single existing Hive installation out there.

Is this a good thing? Should we message it somehow? Should
we coordinate with Hive folks?

Thanks,
Roman.

On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Hello all,
> I have posted a release candidate for Hadoop 1.0.0 at
>    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>
> Please download, evaluate, and vote on this list.
> The artifacts will be posted to the maven repo shortly.
> The vote will close at noon PST on Thursday 15 Dec.

Pulled this RC into Bigtop, built the complete stack and published
packages in the usual place (feel free to install on your own cluster
by just doing yum or puppet installs):
    http://bigtop01.cloudera.org:8080/view/RCs/job/Bigtop-trunk-rc-hadoop-1.0.0-hive-0.8.0/label=centos5/lastSuccessfulBuild/artifact/output/
    http://bigtop01.cloudera.org:8080/view/RCs/job/Bigtop-trunk-rc-hadoop-1.0.0-hive-0.8.0/

Ran test on a fully distributed 5 nodes cluster on EC2 for 10 hours:
    http://bigtop01.cloudera.org:8080/view/RCs/job/Bigtop-rc-smoketest/lastCompletedBuild/#showFailuresLink

The bulk of the failures is in Hive.

At this point I feel like we've got to resolve 3 issues with this release:
   1. Making sure we agree on what to do with *all* of existing Hive
deployemnts
   that are going to be broken by the version change.
   2. Analyzing Mahout 0.5 failures:
       http://bigtop01.cloudera.org:8080/view/RCs/job/Bigtop-rc-smoketest/lastCompletedBuild/testReport/junit/org.apache.bigtop.itest.mahout.smoke/TestMahoutExamples/factorizeMovieLensRatings/
       http://bigtop01.cloudera.org:8080/view/RCs/job/Bigtop-rc-smoketest/lastCompletedBuild/testReport/junit/org.apache.bigtop.itest.mahout.smoke/TestMahoutExamples/testReutersLDA/
   3. Considering a fix for multifilewc

Hope this helps.

Thanks,
Roman.

On Fri, Dec 9, 2011 at 6:29 PM, Ashutosh Chauhan <[EMAIL PROTECTED]> wrote:
> Hey Roman,
>
> That problem is at Hive end. You can try out the patch at
> https://issues.apache.org/jira/browse/HIVE-2631 to unblock your testing.

Btw, I think it is very instructive to take a look at how Linux
community has dealt
with version transition between 2.X -> 3.X. Here's a thread that I still have in
my short term memory. There were, of course, others
     https://plus.google.com/106327083461132854143/posts/SbnL3KaVRtM#106327083461132854143/posts/SbnL3KaVRtM

Thanks,
Roman.

>> Btw, I think it is very instructive to take a look at how
Linux community has dealt
>> with version transition between 2.X -> 3.X.

You mean you want us to not call it 1.0.0?  As I remember the vote was
overwhelmingly
in favor of calling it 1.0.0.
--Matt

On Sat, Dec 10, 2011 at 11:23 AM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:

> On Fri, Dec 9, 2011 at 6:29 PM, Ashutosh Chauhan <[EMAIL PROTECTED]>
> wrote:
> > Hey Roman,
> >
> > That problem is at Hive end. You can try out the patch at
> > https://issues.apache.org/jira/browse/HIVE-2631 to unblock your testing.
>
> Btw, I think it is very instructive to take a look at how Linux
> community has dealt
> with version transition between 2.X -> 3.X. Here's a thread that I still
> have in
> my short term memory. There were, of course, others
>
> https://plus.google.com/106327083461132854143/posts/SbnL3KaVRtM#106327083461132854143/posts/SbnL3KaVRtM
>
> Thanks,
> Roman.
>

On Sat, Dec 10, 2011 at 12:24 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>> Btw, I think it is very instructive to take a look at how
> Linux community has dealt
>>> with version transition between 2.X -> 3.X.
>
> You mean you want us to not call it 1.0.0?  As I remember the vote was
> overwhelmingly
> in favor of calling it 1.0.0.

That's not what I was trying to drive at. Changing versions is fine
as long as there's a clear messaging around it to downstream.

For example, making sure that HIVE-2631 is scheduled for
inclusion into an upcoming Hive 0.8.0 release would greatly
those types of concerns for Hive.

Also having a clear message on a website/etc would help.

On the other hand -- NOT changing versions for quite
a bit of time (to let downstream catch up) is also an
option. That's what experience with Linux versioning
has taught me.

Thanks,
Roman.

Yes, I agree that we, the whole Hadoop development community, need to help
each other get the various components working together, and keep them
mutually compatible as each continues to grow and evolve.  I think BigTop
is providing a valuable service in this area, by providing an official
Apache place for the components to be tested together.
--Matt

On Mon, Dec 12, 2011 at 8:20 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:

> On Sat, Dec 10, 2011 at 12:24 PM, Matt Foley <[EMAIL PROTECTED]>
> wrote:
> >>> Btw, I think it is very instructive to take a look at how
> > Linux community has dealt
> >>> with version transition between 2.X -> 3.X.
> >
> > You mean you want us to not call it 1.0.0?  As I remember the vote was
> > overwhelmingly
> > in favor of calling it 1.0.0.
>
> That's not what I was trying to drive at. Changing versions is fine
> as long as there's a clear messaging around it to downstream.
>
> For example, making sure that HIVE-2631 is scheduled for
> inclusion into an upcoming Hive 0.8.0 release would greatly
> those types of concerns for Hive.
>
> Also having a clear message on a website/etc would help.
>
> On the other hand -- NOT changing versions for quite
> a bit of time (to let downstream catch up) is also an
> option. That's what experience with Linux versioning
> has taught me.
>
> Thanks,
> Roman.
>

fwiw, looks like there is a dependency missing for jackson in the published pom file.

Looks like JobClient imports some of its classes causing Hadoop local mode to fail if running directly from a mvn retrieve etc..

There seems to be a fair number of Cascading/Hadoop sub-projects that do this a lot.

chris

On Dec 9, 2011, at 3:26 PM, Matt Foley wrote:

> Hi Roman,
> regarding MAPREDUCE-3319<https://issues.apache.org/jira/browse/MAPREDUCE-3319>
> I'm
> confused too.  Your comment in the bug as of 28/Nov/11 21:49 seems to
> indicate that it is fixed, but clearly it wasn't fixed the same way as
> Subroto's patch (which came in on Dec 6).
>
> Anyway, I reviewed and committed Subroto's patch to branch-1.  If there is
> a need to regenerate the RC for 1.0.0, I'll merge it to branch-1.0, but I
> hope no one will think this is serious enough to be a cause to regenerate
> the RC just for this patch.
>
> BTW, the same change would be applicable to trunk, so I've left the bug
> open.
>
> --Matt
>
> On Fri, Dec 9, 2011 at 2:47 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:
>
>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>> Hello all,
>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>
>>> Please download, evaluate, and vote on this list.
>>
>> Pulled into Bigtop, built and running integrations tests today.
>>
>> Quick question though: how come this one is not fixed?
>>    https://issues.apache.org/jira/browse/MAPREDUCE-3319
>> There's a patch posted, etc *and* it wasn't reproducible
>> in the branch. I'm confused.
>>
>> Thanks,
>> Roman.
>>

--
Chris K Wensel
[EMAIL PROTECTED]
http://concurrentinc.com

In various emails and jiras, I have been asked to incorporate the following
additional patches in 1.0.0:

   - MAPREDUCE-3319 (Roman)
   - HADOOP-7903 (Arpit)
   - MAPREDUCE-3475 (Daryn)
   - HDFS-2589 (Daryn)
   - HADOOP jira about to be opened (Chris W.) for missing jackson
   dependency in hadoop pom.

I have not heard of any other significant issues in this build.
I will re-spin the release candidate tomorrow.

Thanks,
--Matt

On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:

> Hello all,
> I have posted a release candidate for Hadoop 1.0.0 at
>     http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>
> Please download, evaluate, and vote on this list.
> The artifacts will be posted to the maven repo shortly.
> The vote will close at noon PST on Thursday 15 Dec.
>
> It may be of interest that it is important to use an appropriate version
> of Java.
> I lost several days due to instabilities apparently in Oracle JDK
> 1.6.0_23, which
> caused about 30 junit test failures in contrib (streaming, schedulers, and
> gridmix).
> Switching to JDK 1.6.0_26 made the problems go away.
>
> The release artifacts in this hadoop-1.0.0-rc2 were build with
> JDK 1.6.0_26.
>
> Thank you,
> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>

Chris K Wensel <chris@...> writes:
>
> fwiw, looks like there is a dependency missing for jackson in the published
pom file.

Hi Chris,

there is already an issues for this: HADOOP-7461

Marco
>
> Looks like JobClient imports some of its classes causing Hadoop local mode to
fail if running directly from
> a mvn retrieve etc..
>
> There seems to be a fair number of Cascading/Hadoop sub-projects that do this
a lot.
>
> chris
>
> --
> Chris K Wensel
> chris@...
> http://concurrentinc.com
>
>

Matt,
 I would like to request the following JIRA be included in Hadoop 1.0.0.
  https://issues.apache.org/jira/browse/MAPREDUCE-3475
  https://issues.apache.org/jira/browse/HDFS-2589

Thanks
Mark

On 12/8/11 1:57 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:

> Hello all,
> I have posted a release candidate for Hadoop 1.0.0 at
>     http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>
> Please download, evaluate, and vote on this list.
> The artifacts will be posted to the maven repo shortly.
> The vote will close at noon PST on Thursday 15 Dec.
>
> It may be of interest that it is important to use an appropriate version of
> Java.
> I lost several days due to instabilities apparently in Oracle JDK 1.6.0_23,
> which
> caused about 30 junit test failures in contrib (streaming, schedulers, and
> gridmix).
> Switching to JDK 1.6.0_26 made the problems go away.
>
> The release artifacts in this hadoop-1.0.0-rc2 were build with JDK 1.6.0_26.
>
> Thank you,
> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)

Dear all,
I have a clean build of the below, that passes junit testing, and was about
to post it, when I got email about the newly opened
HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929> "Port
HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
working with secure Hadoop.  Since HBase support is a key element of 1.0.0,
and it seems this will be fixable fairly promptly, I am going to wait
another day for 1.0.0-rc3.

Thanks for your patience,
--Matt

On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]> wrote:

> In various emails and jiras, I have been asked to incorporate the
> following additional patches in 1.0.0:
>
>    - MAPREDUCE-3319 (Roman)
>    - HADOOP-7903 (Arpit)
>    - MAPREDUCE-3475 (Daryn)
>    - HDFS-2589 (Daryn)
>    - HADOOP jira about to be opened (Chris W.) for missing jackson
>    dependency in hadoop pom.
>
> I have not heard of any other significant issues in this build.
> I will re-spin the release candidate tomorrow.
>
> Thanks,
> --Matt
>
> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>
>> Hello all,
>> I have posted a release candidate for Hadoop 1.0.0 at
>>     http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>
>> Please download, evaluate, and vote on this list.
>> The artifacts will be posted to the maven repo shortly.
>> The vote will close at noon PST on Thursday 15 Dec.
>>
>> It may be of interest that it is important to use an appropriate version
>> of Java.
>> I lost several days due to instabilities apparently in Oracle JDK
>> 1.6.0_23, which
>> caused about 30 junit test failures in contrib (streaming, schedulers,
>> and gridmix).
>> Switching to JDK 1.6.0_26 made the problems go away.
>>
>> The release artifacts in this hadoop-1.0.0-rc2 were build with
>> JDK 1.6.0_26.
>>
>> Thank you,
>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>
>
>

On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Dear all,
> I have a clean build of the below, that passes junit testing, and was about
> to post it, when I got email about the newly opened
> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929> "Port
> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
> working with secure Hadoop.  Since HBase support is a key element of 1.0.0,
> and it seems this will be fixable fairly promptly, I am going to wait
> another day for 1.0.0-rc3.
>

Thanks Matt.  Yes, secure hbase needs this.
St.Ack

Hello all,
I have posted a new release candidate for Hadoop 1.0.0 at
    http://people.apache.org/~mattf/hadoop-1.0.0-rc3/

Please download, evaluate, and vote on this list.
The artifacts have also been posted to the maven repo.
The vote will close at 12:30pm PST on Friday 13 Dec.

There had been an issue raised regarding
HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
 This has been evaluated and the jira closed as invalid.  Thanks to Andrew
and others involved for helping assure the quality of this release.

As previously mentioned, use of JDK 1.6.0_26 or better is recommended for
this release.

Thank you,

> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]> wrote:

> Dear all,
> I have a clean build of the below, that passes junit testing, and was
> about to post it, when I got email about the newly opened HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929> "Port
> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
> working with secure Hadoop.  Since HBase support is a key element of 1.0.0,
> and it seems this will be fixable fairly promptly, I am going to wait
> another day for 1.0.0-rc3.
>
> Thanks for your patience,
> --Matt
>
>
> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]>wrote:
>
>> In various emails and jiras, I have been asked to incorporate the
>> following additional patches in 1.0.0:
>>
>>    - MAPREDUCE-3319 (Roman)
>>    - HADOOP-7903 (Arpit)
>>    - MAPREDUCE-3475 (Daryn)
>>    - HDFS-2589 (Daryn)
>>    - HADOOP jira about to be opened (Chris W.) for missing jackson
>>    dependency in hadoop pom.
>>
>> I have not heard of any other significant issues in this build.
>> I will re-spin the release candidate tomorrow.
>>
>> Thanks,
>> --Matt
>>
>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>
>>> Hello all,
>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>     http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>
>>> Please download, evaluate, and vote on this list.
>>> The artifacts will be posted to the maven repo shortly.
>>> The vote will close at noon PST on Thursday 15 Dec.
>>>
>>> It may be of interest that it is important to use an appropriate version
>>> of Java.
>>> I lost several days due to instabilities apparently in Oracle JDK
>>> 1.6.0_23, which
>>> caused about 30 junit test failures in contrib (streaming, schedulers,
>>> and gridmix).
>>> Switching to JDK 1.6.0_26 made the problems go away.
>>>
>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
>>> JDK 1.6.0_26.
>>>
>>> Thank you,
>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>
>>
>>
>

See the last comment on HADOOP-7929.

My working style is to put up a patch that sketches what changes I am thinking, if this is not too labor intensive to produce, even if while concurrently running tests to confirm assumptions. If I have something real, I'll set 'Patch Available'. Apologies if this caused any confusion here, and I can do this differently going forward. (?)

I _still_ don't have a working secure-everything environment with the latest RCs of all of the pieces, but 7929 is a red herring.
 
Best regards,
   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
----- Original Message -----
> From: Stack <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc:
> Sent: Friday, December 16, 2011 9:56 AM
> Subject: Re: [VOTE] Hadoop-1.0.0 release candidate 2
>
> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
> wrote:
>>  Dear all,
>>  I have a clean build of the below, that passes junit testing, and was about
>>  to post it, when I got email about the newly opened
>>  HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>
> "Port
>>  HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>>  working with secure Hadoop.  Since HBase support is a key element of 1.0.0,
>>  and it seems this will be fixable fairly promptly, I am going to wait
>>  another day for 1.0.0-rc3.
>>
>
> Thanks Matt.  Yes, secure hbase needs this.
> St.Ack
>

On Fri, Dec 16, 2011 at 12:10PM, Matt Foley wrote:
> Hello all,
> I have posted a new release candidate for Hadoop 1.0.0 at
>     http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>
> Please download, evaluate, and vote on this list.
> The artifacts have also been posted to the maven repo.
> The vote will close at 12:30pm PST on Friday 13 Dec.

So, the vote has been closed for three days? Ok then ;)

> There had been an issue raised regarding
> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>  This has been evaluated and the jira closed as invalid.  Thanks to Andrew
> and others involved for helping assure the quality of this release.
>
> As previously mentioned, use of JDK 1.6.0_26 or better is recommended for
> this release.
>
> Thank you,
>
> > --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>
>
> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>
> > Dear all,
> > I have a clean build of the below, that passes junit testing, and was
> > about to post it, when I got email about the newly opened HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929> "Port
> > HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
> > working with secure Hadoop.  Since HBase support is a key element of 1.0.0,
> > and it seems this will be fixable fairly promptly, I am going to wait
> > another day for 1.0.0-rc3.
> >
> > Thanks for your patience,
> > --Matt
> >
> >
> > On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]>wrote:
> >
> >> In various emails and jiras, I have been asked to incorporate the
> >> following additional patches in 1.0.0:
> >>
> >>    - MAPREDUCE-3319 (Roman)
> >>    - HADOOP-7903 (Arpit)
> >>    - MAPREDUCE-3475 (Daryn)
> >>    - HDFS-2589 (Daryn)
> >>    - HADOOP jira about to be opened (Chris W.) for missing jackson
> >>    dependency in hadoop pom.
> >>
> >> I have not heard of any other significant issues in this build.
> >> I will re-spin the release candidate tomorrow.
> >>
> >> Thanks,
> >> --Matt
> >>
> >> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
> >>
> >>> Hello all,
> >>> I have posted a release candidate for Hadoop 1.0.0 at
> >>>     http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
> >>>
> >>> Please download, evaluate, and vote on this list.
> >>> The artifacts will be posted to the maven repo shortly.
> >>> The vote will close at noon PST on Thursday 15 Dec.
> >>>
> >>> It may be of interest that it is important to use an appropriate version
> >>> of Java.
> >>> I lost several days due to instabilities apparently in Oracle JDK
> >>> 1.6.0_23, which
> >>> caused about 30 junit test failures in contrib (streaming, schedulers,
> >>> and gridmix).
> >>> Switching to JDK 1.6.0_26 made the problems go away.
> >>>
> >>> The release artifacts in this hadoop-1.0.0-rc2 were build with
> >>> JDK 1.6.0_26.
> >>>
> >>> Thank you,
> >>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
> >>>
> >>
> >>
> >

Hmm, on what year does the 13th next fall on a Friday?

    - Tim.

On Dec 16, 2011, at 6:14 PM, "Konstantin Boudnik" <[EMAIL PROTECTED]> wrote:

> On Fri, Dec 16, 2011 at 12:10PM, Matt Foley wrote:
>> Hello all,
>> I have posted a new release candidate for Hadoop 1.0.0 at
>>    http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>>
>> Please download, evaluate, and vote on this list.
>> The artifacts have also been posted to the maven repo.
>> The vote will close at 12:30pm PST on Friday 13 Dec.
>
> So, the vote has been closed for three days? Ok then ;)
>
>> There had been an issue raised regarding
>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>> This has been evaluated and the jira closed as invalid.  Thanks to Andrew
>> and others involved for helping assure the quality of this release.
>>
>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended for
>> this release.
>>
>> Thank you,
>>
>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>
>>
>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>
>>> Dear all,
>>> I have a clean build of the below, that passes junit testing, and was
>>> about to post it, when I got email about the newly opened HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>>> working with secure Hadoop.  Since HBase support is a key element of 1.0.0,
>>> and it seems this will be fixable fairly promptly, I am going to wait
>>> another day for 1.0.0-rc3.
>>>
>>> Thanks for your patience,
>>> --Matt
>>>
>>>
>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]>wrote:
>>>
>>>> In various emails and jiras, I have been asked to incorporate the
>>>> following additional patches in 1.0.0:
>>>>
>>>>   - MAPREDUCE-3319 (Roman)
>>>>   - HADOOP-7903 (Arpit)
>>>>   - MAPREDUCE-3475 (Daryn)
>>>>   - HDFS-2589 (Daryn)
>>>>   - HADOOP jira about to be opened (Chris W.) for missing jackson
>>>>   dependency in hadoop pom.
>>>>
>>>> I have not heard of any other significant issues in this build.
>>>> I will re-spin the release candidate tomorrow.
>>>>
>>>> Thanks,
>>>> --Matt
>>>>
>>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> Hello all,
>>>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>>>    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>>>
>>>>> Please download, evaluate, and vote on this list.
>>>>> The artifacts will be posted to the maven repo shortly.
>>>>> The vote will close at noon PST on Thursday 15 Dec.
>>>>>
>>>>> It may be of interest that it is important to use an appropriate version
>>>>> of Java.
>>>>> I lost several days due to instabilities apparently in Oracle JDK
>>>>> 1.6.0_23, which
>>>>> caused about 30 junit test failures in contrib (streaming, schedulers,
>>>>> and gridmix).
>>>>> Switching to JDK 1.6.0_26 made the problems go away.
>>>>>
>>>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
>>>>> JDK 1.6.0_26.
>>>>>
>>>>> Thank you,
>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>>
>>>>
>>>>
>>>

The information and any attached documents contained in this message
may be confidential and/or legally privileged.  The message is
intended solely for the addressee(s).  If you are not the intended
recipient, you are hereby notified that any use, dissemination, or
reproduction is strictly prohibited and may be unlawful.  If you are
not the intended recipient, please contact the sender immediately by
return e-mail and destroy all copies of the original message.

Okay guys, obviously I can't add.  Something about a carry bit... :-)
Let's try:
    The vote will close at 12:30pm PST on Friday 23 Dec.

Thank you.
Regards,
--Matt

On Fri, Dec 16, 2011 at 6:44 PM, Tim Broberg <[EMAIL PROTECTED]> wrote:

> Hmm, on what year does the 13th next fall on a Friday?
>
>    - Tim.
>
> On Dec 16, 2011, at 6:14 PM, "Konstantin Boudnik" <[EMAIL PROTECTED]> wrote:
>
> > On Fri, Dec 16, 2011 at 12:10PM, Matt Foley wrote:
> >> Hello all,
> >> I have posted a new release candidate for Hadoop 1.0.0 at
> >>    http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
> >>
> >> Please download, evaluate, and vote on this list.
> >> The artifacts have also been posted to the maven repo.
> >> The vote will close at 12:30pm PST on Friday 13 Dec.
> >
> > So, the vote has been closed for three days? Ok then ;)
> >
> >> There had been an issue raised regarding
> >> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
> >> This has been evaluated and the jira closed as invalid.  Thanks to
> Andrew
> >> and others involved for helping assure the quality of this release.
> >>
> >> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
> for
> >> this release.
> >>
> >> Thank you,
> >>
> >>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
> >>
> >>
> >> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
> wrote:
> >>
> >>> Dear all,
> >>> I have a clean build of the below, that passes junit testing, and was
> >>> about to post it, when I got email about the newly opened HADOOP-7929<
> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
> >>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
> >>> working with secure Hadoop.  Since HBase support is a key element of
> 1.0.0,
> >>> and it seems this will be fixable fairly promptly, I am going to wait
> >>> another day for 1.0.0-rc3.
> >>>
> >>> Thanks for your patience,
> >>> --Matt
> >>>
> >>>
> >>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]
> >wrote:
> >>>
> >>>> In various emails and jiras, I have been asked to incorporate the
> >>>> following additional patches in 1.0.0:
> >>>>
> >>>>   - MAPREDUCE-3319 (Roman)
> >>>>   - HADOOP-7903 (Arpit)
> >>>>   - MAPREDUCE-3475 (Daryn)
> >>>>   - HDFS-2589 (Daryn)
> >>>>   - HADOOP jira about to be opened (Chris W.) for missing jackson
> >>>>   dependency in hadoop pom.
> >>>>
> >>>> I have not heard of any other significant issues in this build.
> >>>> I will re-spin the release candidate tomorrow.
> >>>>
> >>>> Thanks,
> >>>> --Matt
> >>>>
> >>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
> >>>>
> >>>>> Hello all,
> >>>>> I have posted a release candidate for Hadoop 1.0.0 at
> >>>>>    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
> >>>>>
> >>>>> Please download, evaluate, and vote on this list.
> >>>>> The artifacts will be posted to the maven repo shortly.
> >>>>> The vote will close at noon PST on Thursday 15 Dec.
> >>>>>
> >>>>> It may be of interest that it is important to use an appropriate
> version
> >>>>> of Java.
> >>>>> I lost several days due to instabilities apparently in Oracle JDK
> >>>>> 1.6.0_23, which
> >>>>> caused about 30 junit test failures in contrib (streaming,
> schedulers,
> >>>>> and gridmix).
> >>>>> Switching to JDK 1.6.0_26 made the problems go away.
> >>>>>
> >>>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
> >>>>> JDK 1.6.0_26.
> >>>>>
> >>>>> Thank you,
> >>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
> >>>>>
> >>>>
> >>>>
> >>>
>
> The information and any attached documents contained in this message
> may be confidential and/or legally privileged.  The message is
> intended solely for the addressee(s).  If you are not the intended
> recipient, you are hereby notified that any use, dissemination, or
> reproduction is strictly prohibited and may be unlawful.  If you are
> not the intended recipient, please contact the sender immediately by

On Sun, Dec 18, 2011 at 11:18 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Okay guys, obviously I can't add.  Something about a carry bit... :-)
> Let's try:
>    The vote will close at 12:30pm PST on Friday 23 Dec.

Pulled the RC into Bigtop build and constructed a stack with Hadoop 1.0,
HBase 0.92 RC1 and Zookeeper 3.4.1 (everything else being unchanged
from Bigtop's trunk). The packages are available in the usual place:
     http://bigtop01.cloudera.org:8080/view/RCs/job/Bigtop-trunk-rc-hadoop-1.0.0-hbase-0.92.0/label=centos5/lastSuccessfulBuild/artifact/output/
     http://bigtop01.cloudera.org:8080/view/RCs/job/Bigtop-trunk-rc-hadoop-1.0.0-hbase-0.92.0/

Ran 6 hours worth of validation tests and discovered no new regressions.
The MAPREDUCE-3319 has been fixed.

Given all of the above and the fact that HIVE-2631 is now committed
to HIVE's trunk and is scheduled for 0.8.1 from Bigtop's perspective
this RC gets a +1 vote.

Thanks,
Roman.

Which maven repo was updated?

Not seeing anything new in the staging repo
https://repository.apache.org/content/repositories/staging/org/apache/hadoop/hadoop-core/1.0.0/

File dates are Dec 9th.

ckw

On Dec 16, 2011, at 12:10 PM, Matt Foley wrote:

> Hello all,
> I have posted a new release candidate for Hadoop 1.0.0 at
>    http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>
> Please download, evaluate, and vote on this list.
> The artifacts have also been posted to the maven repo.
> The vote will close at 12:30pm PST on Friday 13 Dec.
>
> There had been an issue raised regarding
> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
> This has been evaluated and the jira closed as invalid.  Thanks to Andrew
> and others involved for helping assure the quality of this release.
>
> As previously mentioned, use of JDK 1.6.0_26 or better is recommended for
> this release.
>
> Thank you,
>
>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>
>
> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>
>> Dear all,
>> I have a clean build of the below, that passes junit testing, and was
>> about to post it, when I got email about the newly opened HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>> working with secure Hadoop.  Since HBase support is a key element of 1.0.0,
>> and it seems this will be fixable fairly promptly, I am going to wait
>> another day for 1.0.0-rc3.
>>
>> Thanks for your patience,
>> --Matt
>>
>>
>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]>wrote:
>>
>>> In various emails and jiras, I have been asked to incorporate the
>>> following additional patches in 1.0.0:
>>>
>>>   - MAPREDUCE-3319 (Roman)
>>>   - HADOOP-7903 (Arpit)
>>>   - MAPREDUCE-3475 (Daryn)
>>>   - HDFS-2589 (Daryn)
>>>   - HADOOP jira about to be opened (Chris W.) for missing jackson
>>>   dependency in hadoop pom.
>>>
>>> I have not heard of any other significant issues in this build.
>>> I will re-spin the release candidate tomorrow.
>>>
>>> Thanks,
>>> --Matt
>>>
>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>>
>>>> Hello all,
>>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>>    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>>
>>>> Please download, evaluate, and vote on this list.
>>>> The artifacts will be posted to the maven repo shortly.
>>>> The vote will close at noon PST on Thursday 15 Dec.
>>>>
>>>> It may be of interest that it is important to use an appropriate version
>>>> of Java.
>>>> I lost several days due to instabilities apparently in Oracle JDK
>>>> 1.6.0_23, which
>>>> caused about 30 junit test failures in contrib (streaming, schedulers,
>>>> and gridmix).
>>>> Switching to JDK 1.6.0_26 made the problems go away.
>>>>
>>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
>>>> JDK 1.6.0_26.
>>>>
>>>> Thank you,
>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>
>>>
>>>
>>

--
Chris K Wensel
[EMAIL PROTECTED]
http://concurrentinc.com

Try the following maven version: 1.0.0rc3

Those artifacts are available.

Thanks,
Roman.
On Tue, Dec 20, 2011 at 11:05 AM, Chris K Wensel <[EMAIL PROTECTED]> wrote:
> Which maven repo was updated?
>
> Not seeing anything new in the staging repo
> https://repository.apache.org/content/repositories/staging/org/apache/hadoop/hadoop-core/1.0.0/
>
> File dates are Dec 9th.
>
> ckw
>
> On Dec 16, 2011, at 12:10 PM, Matt Foley wrote:
>
>> Hello all,
>> I have posted a new release candidate for Hadoop 1.0.0 at
>>    http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>>
>> Please download, evaluate, and vote on this list.
>> The artifacts have also been posted to the maven repo.
>> The vote will close at 12:30pm PST on Friday 13 Dec.
>>
>> There had been an issue raised regarding
>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>> This has been evaluated and the jira closed as invalid.  Thanks to Andrew
>> and others involved for helping assure the quality of this release.
>>
>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended for
>> this release.
>>
>> Thank you,
>>
>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>
>>
>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>
>>> Dear all,
>>> I have a clean build of the below, that passes junit testing, and was
>>> about to post it, when I got email about the newly opened HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>>> working with secure Hadoop.  Since HBase support is a key element of 1.0.0,
>>> and it seems this will be fixable fairly promptly, I am going to wait
>>> another day for 1.0.0-rc3.
>>>
>>> Thanks for your patience,
>>> --Matt
>>>
>>>
>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]>wrote:
>>>
>>>> In various emails and jiras, I have been asked to incorporate the
>>>> following additional patches in 1.0.0:
>>>>
>>>>   - MAPREDUCE-3319 (Roman)
>>>>   - HADOOP-7903 (Arpit)
>>>>   - MAPREDUCE-3475 (Daryn)
>>>>   - HDFS-2589 (Daryn)
>>>>   - HADOOP jira about to be opened (Chris W.) for missing jackson
>>>>   dependency in hadoop pom.
>>>>
>>>> I have not heard of any other significant issues in this build.
>>>> I will re-spin the release candidate tomorrow.
>>>>
>>>> Thanks,
>>>> --Matt
>>>>
>>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> Hello all,
>>>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>>>    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>>>
>>>>> Please download, evaluate, and vote on this list.
>>>>> The artifacts will be posted to the maven repo shortly.
>>>>> The vote will close at noon PST on Thursday 15 Dec.
>>>>>
>>>>> It may be of interest that it is important to use an appropriate version
>>>>> of Java.
>>>>> I lost several days due to instabilities apparently in Oracle JDK
>>>>> 1.6.0_23, which
>>>>> caused about 30 junit test failures in contrib (streaming, schedulers,
>>>>> and gridmix).
>>>>> Switching to JDK 1.6.0_26 made the problems go away.
>>>>>
>>>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
>>>>> JDK 1.6.0_26.
>>>>>
>>>>> Thank you,
>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>>
>>>>
>>>>
>>>
>
> --
> Chris K Wensel
> [EMAIL PROTECTED]
> http://concurrentinc.com
>

Chris, thank you very much for bringing this to our attention!
In Nexus, it appears necessary to explicitly "drop" the previous release
candidate before it will show a newer one.  I have now done so, and the
artifacts at

https://repository.apache.org/content/groups/staging/org/apache/hadoop/hadoop-core/1.0.0/
are now correctly dated Dec 16.

Apologies to anyone who inadvertently obtained the old artifacts from the
maven repo.
Thanks,
--Matt

On Tue, Dec 20, 2011 at 12:09 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:

> Try the following maven version: 1.0.0rc3
>
> Those artifacts are available.
>
> Thanks,
> Roman.
>
>
> On Tue, Dec 20, 2011 at 11:05 AM, Chris K Wensel <[EMAIL PROTECTED]> wrote:
> > Which maven repo was updated?
> >
> > Not seeing anything new in the staging repo
> >
> https://repository.apache.org/content/repositories/staging/org/apache/hadoop/hadoop-core/1.0.0/
> >
> > File dates are Dec 9th.
> >
> > ckw
> >
> > On Dec 16, 2011, at 12:10 PM, Matt Foley wrote:
> >
> >> Hello all,
> >> I have posted a new release candidate for Hadoop 1.0.0 at
> >>    http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
> >>
> >> Please download, evaluate, and vote on this list.
> >> The artifacts have also been posted to the maven repo.
> >> The vote will close at 12:30pm PST on Friday 13 Dec.
> >>
> >> There had been an issue raised regarding
> >> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
> >> This has been evaluated and the jira closed as invalid.  Thanks to
> Andrew
> >> and others involved for helping assure the quality of this release.
> >>
> >> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
> for
> >> this release.
> >>
> >> Thank you,
> >>
> >>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
> >>
> >>
> >> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
> wrote:
> >>
> >>> Dear all,
> >>> I have a clean build of the below, that passes junit testing, and was
> >>> about to post it, when I got email about the newly opened HADOOP-7929<
> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
> >>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
> >>> working with secure Hadoop.  Since HBase support is a key element of
> 1.0.0,
> >>> and it seems this will be fixable fairly promptly, I am going to wait
> >>> another day for 1.0.0-rc3.
> >>>
> >>> Thanks for your patience,
> >>> --Matt
> >>>
> >>>
> >>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]
> >wrote:
> >>>
> >>>> In various emails and jiras, I have been asked to incorporate the
> >>>> following additional patches in 1.0.0:
> >>>>
> >>>>   - MAPREDUCE-3319 (Roman)
> >>>>   - HADOOP-7903 (Arpit)
> >>>>   - MAPREDUCE-3475 (Daryn)
> >>>>   - HDFS-2589 (Daryn)
> >>>>   - HADOOP jira about to be opened (Chris W.) for missing jackson
> >>>>   dependency in hadoop pom.
> >>>>
> >>>> I have not heard of any other significant issues in this build.
> >>>> I will re-spin the release candidate tomorrow.
> >>>>
> >>>> Thanks,
> >>>> --Matt
> >>>>
> >>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
> >>>>
> >>>>> Hello all,
> >>>>> I have posted a release candidate for Hadoop 1.0.0 at
> >>>>>    http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
> >>>>>
> >>>>> Please download, evaluate, and vote on this list.
> >>>>> The artifacts will be posted to the maven repo shortly.
> >>>>> The vote will close at noon PST on Thursday 15 Dec.
> >>>>>
> >>>>> It may be of interest that it is important to use an appropriate
> version
> >>>>> of Java.
> >>>>> I lost several days due to instabilities apparently in Oracle JDK
> >>>>> 1.6.0_23, which
> >>>>> caused about 30 junit test failures in contrib (streaming,
> schedulers,
> >>>>> and gridmix).
> >>>>> Switching to JDK 1.6.0_26 made the problems go away.
> >>>>>
> >>>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
> >>>>> JDK 1.6.0_26.
> >>>>>
> >>>>> Thank you,
> >>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)

+1 (non binding)

Ran system tests on both secure and non secure hadoop (20 node clusters) and tests passed with expected results.

--
Arpit
[EMAIL PROTECTED]
On Dec 18, 2011, at 11:18 PM, Matt Foley wrote:

> Okay guys, obviously I can't add.  Something about a carry bit... :-)
> Let's try:
>    The vote will close at 12:30pm PST on Friday 23 Dec.
>
> Thank you.
> Regards,
> --Matt
>
> On Fri, Dec 16, 2011 at 6:44 PM, Tim Broberg <[EMAIL PROTECTED]> wrote:
>
>> Hmm, on what year does the 13th next fall on a Friday?
>>
>>   - Tim.
>>
>> On Dec 16, 2011, at 6:14 PM, "Konstantin Boudnik" <[EMAIL PROTECTED]> wrote:
>>
>>> On Fri, Dec 16, 2011 at 12:10PM, Matt Foley wrote:
>>>> Hello all,
>>>> I have posted a new release candidate for Hadoop 1.0.0 at
>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>>>>
>>>> Please download, evaluate, and vote on this list.
>>>> The artifacts have also been posted to the maven repo.
>>>> The vote will close at 12:30pm PST on Friday 13 Dec.
>>>
>>> So, the vote has been closed for three days? Ok then ;)
>>>
>>>> There had been an issue raised regarding
>>>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>>>> This has been evaluated and the jira closed as invalid.  Thanks to
>> Andrew
>>>> and others involved for helping assure the quality of this release.
>>>>
>>>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
>> for
>>>> this release.
>>>>
>>>> Thank you,
>>>>
>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>
>>>>
>>>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
>> wrote:
>>>>
>>>>> Dear all,
>>>>> I have a clean build of the below, that passes junit testing, and was
>>>>> about to post it, when I got email about the newly opened HADOOP-7929<
>> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>>>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>>>>> working with secure Hadoop.  Since HBase support is a key element of
>> 1.0.0,
>>>>> and it seems this will be fixable fairly promptly, I am going to wait
>>>>> another day for 1.0.0-rc3.
>>>>>
>>>>> Thanks for your patience,
>>>>> --Matt
>>>>>
>>>>>
>>>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]
>>> wrote:
>>>>>
>>>>>> In various emails and jiras, I have been asked to incorporate the
>>>>>> following additional patches in 1.0.0:
>>>>>>
>>>>>>  - MAPREDUCE-3319 (Roman)
>>>>>>  - HADOOP-7903 (Arpit)
>>>>>>  - MAPREDUCE-3475 (Daryn)
>>>>>>  - HDFS-2589 (Daryn)
>>>>>>  - HADOOP jira about to be opened (Chris W.) for missing jackson
>>>>>>  dependency in hadoop pom.
>>>>>>
>>>>>> I have not heard of any other significant issues in this build.
>>>>>> I will re-spin the release candidate tomorrow.
>>>>>>
>>>>>> Thanks,
>>>>>> --Matt
>>>>>>
>>>>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>>> Hello all,
>>>>>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>>>>>
>>>>>>> Please download, evaluate, and vote on this list.
>>>>>>> The artifacts will be posted to the maven repo shortly.
>>>>>>> The vote will close at noon PST on Thursday 15 Dec.
>>>>>>>
>>>>>>> It may be of interest that it is important to use an appropriate
>> version
>>>>>>> of Java.
>>>>>>> I lost several days due to instabilities apparently in Oracle JDK
>>>>>>> 1.6.0_23, which
>>>>>>> caused about 30 junit test failures in contrib (streaming,
>> schedulers,
>>>>>>> and gridmix).
>>>>>>> Switching to JDK 1.6.0_26 made the problems go away.
>>>>>>>
>>>>>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
>>>>>>> JDK 1.6.0_26.
>>>>>>>
>>>>>>> Thank you,
>>>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>
>> The information and any attached documents contained in this message
>> may be confidential and/or legally privileged.  The message is

+1

Checked sigs, ran a single node cluster and tests.

Arun

On Dec 18, 2011, at 11:18 PM, Matt Foley wrote:

> Okay guys, obviously I can't add.  Something about a carry bit... :-)
> Let's try:
>    The vote will close at 12:30pm PST on Friday 23 Dec.
>
> Thank you.
> Regards,
> --Matt
>
> On Fri, Dec 16, 2011 at 6:44 PM, Tim Broberg <[EMAIL PROTECTED]> wrote:
>
>> Hmm, on what year does the 13th next fall on a Friday?
>>
>>   - Tim.
>>
>> On Dec 16, 2011, at 6:14 PM, "Konstantin Boudnik" <[EMAIL PROTECTED]> wrote:
>>
>>> On Fri, Dec 16, 2011 at 12:10PM, Matt Foley wrote:
>>>> Hello all,
>>>> I have posted a new release candidate for Hadoop 1.0.0 at
>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>>>>
>>>> Please download, evaluate, and vote on this list.
>>>> The artifacts have also been posted to the maven repo.
>>>> The vote will close at 12:30pm PST on Friday 13 Dec.
>>>
>>> So, the vote has been closed for three days? Ok then ;)
>>>
>>>> There had been an issue raised regarding
>>>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>>>> This has been evaluated and the jira closed as invalid.  Thanks to
>> Andrew
>>>> and others involved for helping assure the quality of this release.
>>>>
>>>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
>> for
>>>> this release.
>>>>
>>>> Thank you,
>>>>
>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>
>>>>
>>>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
>> wrote:
>>>>
>>>>> Dear all,
>>>>> I have a clean build of the below, that passes junit testing, and was
>>>>> about to post it, when I got email about the newly opened HADOOP-7929<
>> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>>>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>>>>> working with secure Hadoop.  Since HBase support is a key element of
>> 1.0.0,
>>>>> and it seems this will be fixable fairly promptly, I am going to wait
>>>>> another day for 1.0.0-rc3.
>>>>>
>>>>> Thanks for your patience,
>>>>> --Matt
>>>>>
>>>>>
>>>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]
>>> wrote:
>>>>>
>>>>>> In various emails and jiras, I have been asked to incorporate the
>>>>>> following additional patches in 1.0.0:
>>>>>>
>>>>>>  - MAPREDUCE-3319 (Roman)
>>>>>>  - HADOOP-7903 (Arpit)
>>>>>>  - MAPREDUCE-3475 (Daryn)
>>>>>>  - HDFS-2589 (Daryn)
>>>>>>  - HADOOP jira about to be opened (Chris W.) for missing jackson
>>>>>>  dependency in hadoop pom.
>>>>>>
>>>>>> I have not heard of any other significant issues in this build.
>>>>>> I will re-spin the release candidate tomorrow.
>>>>>>
>>>>>> Thanks,
>>>>>> --Matt
>>>>>>
>>>>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>>> Hello all,
>>>>>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>>>>>
>>>>>>> Please download, evaluate, and vote on this list.
>>>>>>> The artifacts will be posted to the maven repo shortly.
>>>>>>> The vote will close at noon PST on Thursday 15 Dec.
>>>>>>>
>>>>>>> It may be of interest that it is important to use an appropriate
>> version
>>>>>>> of Java.
>>>>>>> I lost several days due to instabilities apparently in Oracle JDK
>>>>>>> 1.6.0_23, which
>>>>>>> caused about 30 junit test failures in contrib (streaming,
>> schedulers,
>>>>>>> and gridmix).
>>>>>>> Switching to JDK 1.6.0_26 made the problems go away.
>>>>>>>
>>>>>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
>>>>>>> JDK 1.6.0_26.
>>>>>>>
>>>>>>> Thank you,
>>>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>
>> The information and any attached documents contained in this message
>> may be confidential and/or legally privileged.  The message is
>> intended solely for the addressee(s).  If you are not the intended
>> recipient, you are hereby notified that any use, dissemination, or

+1 ran a single node cluster and a couple of examples on it. Also ran ant
tests.

thanks
mahadev
On Thu, Dec 22, 2011 at 10:23 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:

> +1
>
> Checked sigs, ran a single node cluster and tests.
>
> Arun
>
> On Dec 18, 2011, at 11:18 PM, Matt Foley wrote:
>
> > Okay guys, obviously I can't add.  Something about a carry bit... :-)
> > Let's try:
> >    The vote will close at 12:30pm PST on Friday 23 Dec.
> >
> > Thank you.
> > Regards,
> > --Matt
> >
> > On Fri, Dec 16, 2011 at 6:44 PM, Tim Broberg <[EMAIL PROTECTED]>
> wrote:
> >
> >> Hmm, on what year does the 13th next fall on a Friday?
> >>
> >>   - Tim.
> >>
> >> On Dec 16, 2011, at 6:14 PM, "Konstantin Boudnik" <[EMAIL PROTECTED]>
> wrote:
> >>
> >>> On Fri, Dec 16, 2011 at 12:10PM, Matt Foley wrote:
> >>>> Hello all,
> >>>> I have posted a new release candidate for Hadoop 1.0.0 at
> >>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
> >>>>
> >>>> Please download, evaluate, and vote on this list.
> >>>> The artifacts have also been posted to the maven repo.
> >>>> The vote will close at 12:30pm PST on Friday 13 Dec.
> >>>
> >>> So, the vote has been closed for three days? Ok then ;)
> >>>
> >>>> There had been an issue raised regarding
> >>>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
> >>>> This has been evaluated and the jira closed as invalid.  Thanks to
> >> Andrew
> >>>> and others involved for helping assure the quality of this release.
> >>>>
> >>>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
> >> for
> >>>> this release.
> >>>>
> >>>> Thank you,
> >>>>
> >>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
> >>>>
> >>>>
> >>>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
> >> wrote:
> >>>>
> >>>>> Dear all,
> >>>>> I have a clean build of the below, that passes junit testing, and was
> >>>>> about to post it, when I got email about the newly opened
> HADOOP-7929<
> >> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
> >>>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
> >>>>> working with secure Hadoop.  Since HBase support is a key element of
> >> 1.0.0,
> >>>>> and it seems this will be fixable fairly promptly, I am going to wait
> >>>>> another day for 1.0.0-rc3.
> >>>>>
> >>>>> Thanks for your patience,
> >>>>> --Matt
> >>>>>
> >>>>>
> >>>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]
> >>> wrote:
> >>>>>
> >>>>>> In various emails and jiras, I have been asked to incorporate the
> >>>>>> following additional patches in 1.0.0:
> >>>>>>
> >>>>>>  - MAPREDUCE-3319 (Roman)
> >>>>>>  - HADOOP-7903 (Arpit)
> >>>>>>  - MAPREDUCE-3475 (Daryn)
> >>>>>>  - HDFS-2589 (Daryn)
> >>>>>>  - HADOOP jira about to be opened (Chris W.) for missing jackson
> >>>>>>  dependency in hadoop pom.
> >>>>>>
> >>>>>> I have not heard of any other significant issues in this build.
> >>>>>> I will re-spin the release candidate tomorrow.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> --Matt
> >>>>>>
> >>>>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]>
> wrote:
> >>>>>>
> >>>>>>> Hello all,
> >>>>>>> I have posted a release candidate for Hadoop 1.0.0 at
> >>>>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
> >>>>>>>
> >>>>>>> Please download, evaluate, and vote on this list.
> >>>>>>> The artifacts will be posted to the maven repo shortly.
> >>>>>>> The vote will close at noon PST on Thursday 15 Dec.
> >>>>>>>
> >>>>>>> It may be of interest that it is important to use an appropriate
> >> version
> >>>>>>> of Java.
> >>>>>>> I lost several days due to instabilities apparently in Oracle JDK
> >>>>>>> 1.6.0_23, which
> >>>>>>> caused about 30 junit test failures in contrib (streaming,
> >> schedulers,
> >>>>>>> and gridmix).
> >>>>>>> Switching to JDK 1.6.0_26 made the problems go away.
> >>>>>>>
> >>>>>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
> >>>>>>> JDK 1.6.0_26.

+1

I verified checksums and signatures, and successfully ran some MapReduce jobs.

I also ran an API compatibility check against the previous release
(https://issues.apache.org/jira/browse/HADOOP-7035) and it passed.

Cheers,
Tom

On Fri, Dec 16, 2011 at 12:10 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Hello all,
> I have posted a new release candidate for Hadoop 1.0.0 at
>    http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>
> Please download, evaluate, and vote on this list.
> The artifacts have also been posted to the maven repo.
> The vote will close at 12:30pm PST on Friday 13 Dec.
>
> There had been an issue raised regarding
> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>  This has been evaluated and the jira closed as invalid.  Thanks to Andrew
> and others involved for helping assure the quality of this release.
>
> As previously mentioned, use of JDK 1.6.0_26 or better is recommended for
> this release.
>
> Thank you,
>
>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>
>
> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>
>> Dear all,
>> I have a clean build of the below, that passes junit testing, and was
>> about to post it, when I got email about the newly opened HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>> working with secure Hadoop.  Since HBase support is a key element of 1.0.0,
>> and it seems this will be fixable fairly promptly, I am going to wait
>> another day for 1.0.0-rc3.
>>
>> Thanks for your patience,
>> --Matt
>>
>>
>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]>wrote:
>>
>>> In various emails and jiras, I have been asked to incorporate the
>>> following additional patches in 1.0.0:
>>>
>>>    - MAPREDUCE-3319 (Roman)
>>>    - HADOOP-7903 (Arpit)
>>>    - MAPREDUCE-3475 (Daryn)
>>>    - HDFS-2589 (Daryn)
>>>    - HADOOP jira about to be opened (Chris W.) for missing jackson
>>>    dependency in hadoop pom.
>>>
>>> I have not heard of any other significant issues in this build.
>>> I will re-spin the release candidate tomorrow.
>>>
>>> Thanks,
>>> --Matt
>>>
>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>>
>>>> Hello all,
>>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>>     http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>>
>>>> Please download, evaluate, and vote on this list.
>>>> The artifacts will be posted to the maven repo shortly.
>>>> The vote will close at noon PST on Thursday 15 Dec.
>>>>
>>>> It may be of interest that it is important to use an appropriate version
>>>> of Java.
>>>> I lost several days due to instabilities apparently in Oracle JDK
>>>> 1.6.0_23, which
>>>> caused about 30 junit test failures in contrib (streaming, schedulers,
>>>> and gridmix).
>>>> Switching to JDK 1.6.0_26 made the problems go away.
>>>>
>>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
>>>> JDK 1.6.0_26.
>>>>
>>>> Thank you,
>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>
>>>
>>>
>>

fwiw, still seeing some dependency issues preventing Cascading tests from passing.

I've only changed mvn dependencies from 20.2 to 1.0.0 and now see

java.io.IOException: java.lang.NoClassDefFoundError: javax/ws/rs/core/StreamingOutput

jackson is now indeed being pulled down and included.

ckw

On Dec 20, 2011, at 1:57 PM, Matt Foley wrote:

> Chris, thank you very much for bringing this to our attention!
> In Nexus, it appears necessary to explicitly "drop" the previous release
> candidate before it will show a newer one.  I have now done so, and the
> artifacts at
>
> https://repository.apache.org/content/groups/staging/org/apache/hadoop/hadoop-core/1.0.0/
> are now correctly dated Dec 16.
>
> Apologies to anyone who inadvertently obtained the old artifacts from the
> maven repo.
> Thanks,
> --Matt
>
> On Tue, Dec 20, 2011 at 12:09 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:
>
>> Try the following maven version: 1.0.0rc3
>>
>> Those artifacts are available.
>>
>> Thanks,
>> Roman.
>>
>>
>> On Tue, Dec 20, 2011 at 11:05 AM, Chris K Wensel <[EMAIL PROTECTED]> wrote:
>>> Which maven repo was updated?
>>>
>>> Not seeing anything new in the staging repo
>>>
>> https://repository.apache.org/content/repositories/staging/org/apache/hadoop/hadoop-core/1.0.0/
>>>
>>> File dates are Dec 9th.
>>>
>>> ckw
>>>
>>> On Dec 16, 2011, at 12:10 PM, Matt Foley wrote:
>>>
>>>> Hello all,
>>>> I have posted a new release candidate for Hadoop 1.0.0 at
>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>>>>
>>>> Please download, evaluate, and vote on this list.
>>>> The artifacts have also been posted to the maven repo.
>>>> The vote will close at 12:30pm PST on Friday 13 Dec.
>>>>
>>>> There had been an issue raised regarding
>>>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>>>> This has been evaluated and the jira closed as invalid.  Thanks to
>> Andrew
>>>> and others involved for helping assure the quality of this release.
>>>>
>>>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
>> for
>>>> this release.
>>>>
>>>> Thank you,
>>>>
>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>
>>>>
>>>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
>> wrote:
>>>>
>>>>> Dear all,
>>>>> I have a clean build of the below, that passes junit testing, and was
>>>>> about to post it, when I got email about the newly opened HADOOP-7929<
>> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>>>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>>>>> working with secure Hadoop.  Since HBase support is a key element of
>> 1.0.0,
>>>>> and it seems this will be fixable fairly promptly, I am going to wait
>>>>> another day for 1.0.0-rc3.
>>>>>
>>>>> Thanks for your patience,
>>>>> --Matt
>>>>>
>>>>>
>>>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]
>>> wrote:
>>>>>
>>>>>> In various emails and jiras, I have been asked to incorporate the
>>>>>> following additional patches in 1.0.0:
>>>>>>
>>>>>>  - MAPREDUCE-3319 (Roman)
>>>>>>  - HADOOP-7903 (Arpit)
>>>>>>  - MAPREDUCE-3475 (Daryn)
>>>>>>  - HDFS-2589 (Daryn)
>>>>>>  - HADOOP jira about to be opened (Chris W.) for missing jackson
>>>>>>  dependency in hadoop pom.
>>>>>>
>>>>>> I have not heard of any other significant issues in this build.
>>>>>> I will re-spin the release candidate tomorrow.
>>>>>>
>>>>>> Thanks,
>>>>>> --Matt
>>>>>>
>>>>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>>> Hello all,
>>>>>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>>>>>
>>>>>>> Please download, evaluate, and vote on this list.
>>>>>>> The artifacts will be posted to the maven repo shortly.
>>>>>>> The vote will close at noon PST on Thursday 15 Dec.
>>>>>>>
>>>>>>> It may be of interest that it is important to use an appropriate
>> version
>>>>>
Chris K Wensel
[EMAIL PROTECTED]
http://concurrentinc.com

Hi Chris,
Please open a jira and post the specific test(s) that are failing, and
we'll try to help track it down.
Since no one else posted problems, and the RC did pass our system tests,
I'm going to go ahead
and declare the vote accepted.  If this turns out to be something serious,
we can spin a patch release.

Thanks,
--Matt

On Fri, Dec 23, 2011 at 10:28 AM, Chris K Wensel <[EMAIL PROTECTED]> wrote:

> fwiw, still seeing some dependency issues preventing Cascading tests from
> passing.
>
> I've only changed mvn dependencies from 20.2 to 1.0.0 and now see
>
> java.io.IOException: java.lang.NoClassDefFoundError:
> javax/ws/rs/core/StreamingOutput
>
> jackson is now indeed being pulled down and included.
>
> ckw
>
> On Dec 20, 2011, at 1:57 PM, Matt Foley wrote:
>
> > Chris, thank you very much for bringing this to our attention!
> > In Nexus, it appears necessary to explicitly "drop" the previous release
> > candidate before it will show a newer one.  I have now done so, and the
> > artifacts at
> >
> >
> https://repository.apache.org/content/groups/staging/org/apache/hadoop/hadoop-core/1.0.0/
> > are now correctly dated Dec 16.
> >
> > Apologies to anyone who inadvertently obtained the old artifacts from the
> > maven repo.
> > Thanks,
> > --Matt
> >
> > On Tue, Dec 20, 2011 at 12:09 PM, Roman Shaposhnik <[EMAIL PROTECTED]>
> wrote:
> >
> >> Try the following maven version: 1.0.0rc3
> >>
> >> Those artifacts are available.
> >>
> >> Thanks,
> >> Roman.
> >>
> >>
> >> On Tue, Dec 20, 2011 at 11:05 AM, Chris K Wensel <[EMAIL PROTECTED]>
> wrote:
> >>> Which maven repo was updated?
> >>>
> >>> Not seeing anything new in the staging repo
> >>>
> >>
> https://repository.apache.org/content/repositories/staging/org/apache/hadoop/hadoop-core/1.0.0/
> >>>
> >>> File dates are Dec 9th.
> >>>
> >>> ckw
> >>>
> >>> On Dec 16, 2011, at 12:10 PM, Matt Foley wrote:
> >>>
> >>>> Hello all,
> >>>> I have posted a new release candidate for Hadoop 1.0.0 at
> >>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
> >>>>
> >>>> Please download, evaluate, and vote on this list.
> >>>> The artifacts have also been posted to the maven repo.
> >>>> The vote will close at 12:30pm PST on Friday 13 Dec.
> >>>>
> >>>> There had been an issue raised regarding
> >>>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
> >>>> This has been evaluated and the jira closed as invalid.  Thanks to
> >> Andrew
> >>>> and others involved for helping assure the quality of this release.
> >>>>
> >>>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
> >> for
> >>>> this release.
> >>>>
> >>>> Thank you,
> >>>>
> >>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
> >>>>
> >>>>
> >>>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
> >> wrote:
> >>>>
> >>>>> Dear all,
> >>>>> I have a clean build of the below, that passes junit testing, and was
> >>>>> about to post it, when I got email about the newly opened
> HADOOP-7929<
> >> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
> >>>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
> >>>>> working with secure Hadoop.  Since HBase support is a key element of
> >> 1.0.0,
> >>>>> and it seems this will be fixable fairly promptly, I am going to wait
> >>>>> another day for 1.0.0-rc3.
> >>>>>
> >>>>> Thanks for your patience,
> >>>>> --Matt
> >>>>>
> >>>>>
> >>>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]
> >>> wrote:
> >>>>>
> >>>>>> In various emails and jiras, I have been asked to incorporate the
> >>>>>> following additional patches in 1.0.0:
> >>>>>>
> >>>>>>  - MAPREDUCE-3319 (Roman)
> >>>>>>  - HADOOP-7903 (Arpit)
> >>>>>>  - MAPREDUCE-3475 (Daryn)
> >>>>>>  - HDFS-2589 (Daryn)
> >>>>>>  - HADOOP jira about to be opened (Chris W.) for missing jackson
> >>>>>>  dependency in hadoop pom.
> >>>>>>
> >>>>>> I have not heard of any other significant issues in this build.
> >>>>>> I will re-spin the release candidate tomorrow.

That's because of the missing jersey dependencies in hadoop-core pom
and that you're using the minicluster stuff that will pull in the
webhdfs classes. A work around would be adding jersey-* dependencies
(cf. hadoop ivy.xml) to your pom in test scope.

There is no perfect solution to this problem (as long as we have only
one hadoop-core artifact), as you don't want to add server
dependencies in hadoop core pom, when common downstream usage is just
the client stuff.

On Fri, Dec 23, 2011 at 10:28 AM, Chris K Wensel <[EMAIL PROTECTED]> wrote:
> fwiw, still seeing some dependency issues preventing Cascading tests from passing.
>
> I've only changed mvn dependencies from 20.2 to 1.0.0 and now see
>
> java.io.IOException: java.lang.NoClassDefFoundError: javax/ws/rs/core/StreamingOutput
>
> jackson is now indeed being pulled down and included.
>
> ckw
>
> On Dec 20, 2011, at 1:57 PM, Matt Foley wrote:
>
>> Chris, thank you very much for bringing this to our attention!
>> In Nexus, it appears necessary to explicitly "drop" the previous release
>> candidate before it will show a newer one.  I have now done so, and the
>> artifacts at
>>
>> https://repository.apache.org/content/groups/staging/org/apache/hadoop/hadoop-core/1.0.0/
>> are now correctly dated Dec 16.
>>
>> Apologies to anyone who inadvertently obtained the old artifacts from the
>> maven repo.
>> Thanks,
>> --Matt
>>
>> On Tue, Dec 20, 2011 at 12:09 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:
>>
>>> Try the following maven version: 1.0.0rc3
>>>
>>> Those artifacts are available.
>>>
>>> Thanks,
>>> Roman.
>>>
>>>
>>> On Tue, Dec 20, 2011 at 11:05 AM, Chris K Wensel <[EMAIL PROTECTED]> wrote:
>>>> Which maven repo was updated?
>>>>
>>>> Not seeing anything new in the staging repo
>>>>
>>> https://repository.apache.org/content/repositories/staging/org/apache/hadoop/hadoop-core/1.0.0/
>>>>
>>>> File dates are Dec 9th.
>>>>
>>>> ckw
>>>>
>>>> On Dec 16, 2011, at 12:10 PM, Matt Foley wrote:
>>>>
>>>>> Hello all,
>>>>> I have posted a new release candidate for Hadoop 1.0.0 at
>>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>>>>>
>>>>> Please download, evaluate, and vote on this list.
>>>>> The artifacts have also been posted to the maven repo.
>>>>> The vote will close at 12:30pm PST on Friday 13 Dec.
>>>>>
>>>>> There had been an issue raised regarding
>>>>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>>>>> This has been evaluated and the jira closed as invalid.  Thanks to
>>> Andrew
>>>>> and others involved for helping assure the quality of this release.
>>>>>
>>>>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
>>> for
>>>>> this release.
>>>>>
>>>>> Thank you,
>>>>>
>>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>>
>>>>>
>>>>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
>>> wrote:
>>>>>
>>>>>> Dear all,
>>>>>> I have a clean build of the below, that passes junit testing, and was
>>>>>> about to post it, when I got email about the newly opened HADOOP-7929<
>>> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>>>>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>>>>>> working with secure Hadoop.  Since HBase support is a key element of
>>> 1.0.0,
>>>>>> and it seems this will be fixable fairly promptly, I am going to wait
>>>>>> another day for 1.0.0-rc3.
>>>>>>
>>>>>> Thanks for your patience,
>>>>>> --Matt
>>>>>>
>>>>>>
>>>>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]
>>>> wrote:
>>>>>>
>>>>>>> In various emails and jiras, I have been asked to incorporate the
>>>>>>> following additional patches in 1.0.0:
>>>>>>>
>>>>>>>  - MAPREDUCE-3319 (Roman)
>>>>>>>  - HADOOP-7903 (Arpit)
>>>>>>>  - MAPREDUCE-3475 (Daryn)
>>>>>>>  - HDFS-2589 (Daryn)
>>>>>>>  - HADOOP jira about to be opened (Chris W.) for missing jackson
>>>>>>>  dependency in hadoop pom.
>>>>>>>
>>>>>>> I have not heard of any other significant issues in this build.

And I also vote +1.

I am delighted to announce that the Release 1.0.0 vote has passed, with
count:
    +1:  6 votes, including 3 PMC members
    -1:   no votes

The publication process is underway, and I will announce it on
general@tomorrow, after the required propagation time.

Best regards,
--Matt
Release Manager

On Fri, Dec 16, 2011 at 12:10 PM, Matt Foley <[EMAIL PROTECTED]> wrote:

> Hello all,
> I have posted a new release candidate for Hadoop 1.0.0 at
>     http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>
> Please download, evaluate, and vote on this list.
> The artifacts have also been posted to the maven repo.
> The vote will close at 12:30pm PST on Friday 13 Dec.
>
> There had been an issue raised regarding HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>  This has been evaluated and the jira closed as invalid.  Thanks to Andrew
> and others involved for helping assure the quality of this release.
>
> As previously mentioned, use of JDK 1.6.0_26 or better is recommended for
> this release.
>
> Thank you,
>
>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>
>
> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>wrote:
>
>> Dear all,
>> I have a clean build of the below, that passes junit testing, and was
>> about to post it, when I got email about the newly opened HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>> working with secure Hadoop.  Since HBase support is a key element of 1.0.0,
>> and it seems this will be fixable fairly promptly, I am going to wait
>> another day for 1.0.0-rc3.
>>
>> Thanks for your patience,
>> --Matt
>>
>>
>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]>wrote:
>>
>>> In various emails and jiras, I have been asked to incorporate the
>>> following additional patches in 1.0.0:
>>>
>>>    - MAPREDUCE-3319 (Roman)
>>>    - HADOOP-7903 (Arpit)
>>>    - MAPREDUCE-3475 (Daryn)
>>>    - HDFS-2589 (Daryn)
>>>    - HADOOP jira about to be opened (Chris W.) for missing jackson
>>>    dependency in hadoop pom.
>>>
>>> I have not heard of any other significant issues in this build.
>>> I will re-spin the release candidate tomorrow.
>>>
>>> Thanks,
>>> --Matt
>>>
>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <[EMAIL PROTECTED]> wrote:
>>>
>>>> Hello all,
>>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>>     http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>>
>>>> Please download, evaluate, and vote on this list.
>>>> The artifacts will be posted to the maven repo shortly.
>>>> The vote will close at noon PST on Thursday 15 Dec.
>>>>
>>>> It may be of interest that it is important to use an appropriate
>>>> version of Java.
>>>> I lost several days due to instabilities apparently in Oracle JDK
>>>> 1.6.0_23, which
>>>> caused about 30 junit test failures in contrib (streaming, schedulers,
>>>> and gridmix).
>>>> Switching to JDK 1.6.0_26 made the problems go away.
>>>>
>>>> The release artifacts in this hadoop-1.0.0-rc2 were build with
>>>> JDK 1.6.0_26.
>>>>
>>>> Thank you,
>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>
>>>
>>>
>>
>

Hadoop tests aren't failing, Cascading tests fail because the Hadoop 1.0.0 pom does not declare all its runtime dependencies as the previous pom's did.

Do what you will.

ckw

On Dec 23, 2011, at 1:50 PM, Matt Foley wrote:

> Hi Chris,
> Please open a jira and post the specific test(s) that are failing, and
> we'll try to help track it down.
> Since no one else posted problems, and the RC did pass our system tests,
> I'm going to go ahead
> and declare the vote accepted.  If this turns out to be something serious,
> we can spin a patch release.
>
> Thanks,
> --Matt
>
> On Fri, Dec 23, 2011 at 10:28 AM, Chris K Wensel <[EMAIL PROTECTED]> wrote:
>
>> fwiw, still seeing some dependency issues preventing Cascading tests from
>> passing.
>>
>> I've only changed mvn dependencies from 20.2 to 1.0.0 and now see
>>
>> java.io.IOException: java.lang.NoClassDefFoundError:
>> javax/ws/rs/core/StreamingOutput
>>
>> jackson is now indeed being pulled down and included.
>>
>> ckw
>>
>> On Dec 20, 2011, at 1:57 PM, Matt Foley wrote:
>>
>>> Chris, thank you very much for bringing this to our attention!
>>> In Nexus, it appears necessary to explicitly "drop" the previous release
>>> candidate before it will show a newer one.  I have now done so, and the
>>> artifacts at
>>>
>>>
>> https://repository.apache.org/content/groups/staging/org/apache/hadoop/hadoop-core/1.0.0/
>>> are now correctly dated Dec 16.
>>>
>>> Apologies to anyone who inadvertently obtained the old artifacts from the
>>> maven repo.
>>> Thanks,
>>> --Matt
>>>
>>> On Tue, Dec 20, 2011 at 12:09 PM, Roman Shaposhnik <[EMAIL PROTECTED]>
>> wrote:
>>>
>>>> Try the following maven version: 1.0.0rc3
>>>>
>>>> Those artifacts are available.
>>>>
>>>> Thanks,
>>>> Roman.
>>>>
>>>>
>>>> On Tue, Dec 20, 2011 at 11:05 AM, Chris K Wensel <[EMAIL PROTECTED]>
>> wrote:
>>>>> Which maven repo was updated?
>>>>>
>>>>> Not seeing anything new in the staging repo
>>>>>
>>>>
>> https://repository.apache.org/content/repositories/staging/org/apache/hadoop/hadoop-core/1.0.0/
>>>>>
>>>>> File dates are Dec 9th.
>>>>>
>>>>> ckw
>>>>>
>>>>> On Dec 16, 2011, at 12:10 PM, Matt Foley wrote:
>>>>>
>>>>>> Hello all,
>>>>>> I have posted a new release candidate for Hadoop 1.0.0 at
>>>>>>  http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>>>>>>
>>>>>> Please download, evaluate, and vote on this list.
>>>>>> The artifacts have also been posted to the maven repo.
>>>>>> The vote will close at 12:30pm PST on Friday 13 Dec.
>>>>>>
>>>>>> There had been an issue raised regarding
>>>>>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>>>>>> This has been evaluated and the jira closed as invalid.  Thanks to
>>>> Andrew
>>>>>> and others involved for helping assure the quality of this release.
>>>>>>
>>>>>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
>>>> for
>>>>>> this release.
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>>>
>>>>>>
>>>>>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
>>>> wrote:
>>>>>>
>>>>>>> Dear all,
>>>>>>> I have a clean build of the below, that passes junit testing, and was
>>>>>>> about to post it, when I got email about the newly opened
>> HADOOP-7929<
>>>> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>>>>>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>>>>>>> working with secure Hadoop.  Since HBase support is a key element of
>>>> 1.0.0,
>>>>>>> and it seems this will be fixable fairly promptly, I am going to wait
>>>>>>> another day for 1.0.0-rc3.
>>>>>>>
>>>>>>> Thanks for your patience,
>>>>>>> --Matt
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]
>>>>> wrote:
>>>>>>>
>>>>>>>> In various emails and jiras, I have been asked to incorporate the
>>>>>>>> following additional patches in 1.0.0:
>>>>>>>>
>>>>>>>> - MAPREDUCE-3319 (Roman)
>>>>>>>> - HADOOP-7903 (Arpit)

Chris K Wensel
[EMAIL PROTECTED]
http://concurrentinc.com

I simply added the jax-rs jsr mvn runtime dependency to my test runtime, but it isn't my dependency, it is hadoop's.

worked before in previous releases, doesn't work now in 1.0 without extra steps on my part (and likely others downstream).

just sayin'...

ckw

On Dec 23, 2011, at 2:03 PM, Luke Lu wrote:

> That's because of the missing jersey dependencies in hadoop-core pom
> and that you're using the minicluster stuff that will pull in the
> webhdfs classes. A work around would be adding jersey-* dependencies
> (cf. hadoop ivy.xml) to your pom in test scope.
>
> There is no perfect solution to this problem (as long as we have only
> one hadoop-core artifact), as you don't want to add server
> dependencies in hadoop core pom, when common downstream usage is just
> the client stuff.
>
> On Fri, Dec 23, 2011 at 10:28 AM, Chris K Wensel <[EMAIL PROTECTED]> wrote:
>> fwiw, still seeing some dependency issues preventing Cascading tests from passing.
>>
>> I've only changed mvn dependencies from 20.2 to 1.0.0 and now see
>>
>> java.io.IOException: java.lang.NoClassDefFoundError: javax/ws/rs/core/StreamingOutput
>>
>> jackson is now indeed being pulled down and included.
>>
>> ckw
>>
>> On Dec 20, 2011, at 1:57 PM, Matt Foley wrote:
>>
>>> Chris, thank you very much for bringing this to our attention!
>>> In Nexus, it appears necessary to explicitly "drop" the previous release
>>> candidate before it will show a newer one.  I have now done so, and the
>>> artifacts at
>>>
>>> https://repository.apache.org/content/groups/staging/org/apache/hadoop/hadoop-core/1.0.0/
>>> are now correctly dated Dec 16.
>>>
>>> Apologies to anyone who inadvertently obtained the old artifacts from the
>>> maven repo.
>>> Thanks,
>>> --Matt
>>>
>>> On Tue, Dec 20, 2011 at 12:09 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:
>>>
>>>> Try the following maven version: 1.0.0rc3
>>>>
>>>> Those artifacts are available.
>>>>
>>>> Thanks,
>>>> Roman.
>>>>
>>>>
>>>> On Tue, Dec 20, 2011 at 11:05 AM, Chris K Wensel <[EMAIL PROTECTED]> wrote:
>>>>> Which maven repo was updated?
>>>>>
>>>>> Not seeing anything new in the staging repo
>>>>>
>>>> https://repository.apache.org/content/repositories/staging/org/apache/hadoop/hadoop-core/1.0.0/
>>>>>
>>>>> File dates are Dec 9th.
>>>>>
>>>>> ckw
>>>>>
>>>>> On Dec 16, 2011, at 12:10 PM, Matt Foley wrote:
>>>>>
>>>>>> Hello all,
>>>>>> I have posted a new release candidate for Hadoop 1.0.0 at
>>>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>>>>>>
>>>>>> Please download, evaluate, and vote on this list.
>>>>>> The artifacts have also been posted to the maven repo.
>>>>>> The vote will close at 12:30pm PST on Friday 13 Dec.
>>>>>>
>>>>>> There had been an issue raised regarding
>>>>>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>>>>>> This has been evaluated and the jira closed as invalid.  Thanks to
>>>> Andrew
>>>>>> and others involved for helping assure the quality of this release.
>>>>>>
>>>>>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
>>>> for
>>>>>> this release.
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>>>
>>>>>>
>>>>>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <[EMAIL PROTECTED]>
>>>> wrote:
>>>>>>
>>>>>>> Dear all,
>>>>>>> I have a clean build of the below, that passes junit testing, and was
>>>>>>> about to post it, when I got email about the newly opened HADOOP-7929<
>>>> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>>>>>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase from
>>>>>>> working with secure Hadoop.  Since HBase support is a key element of
>>>> 1.0.0,
>>>>>>> and it seems this will be fixable fairly promptly, I am going to wait
>>>>>>> another day for 1.0.0-rc3.
>>>>>>>
>>>>>>> Thanks for your patience,
>>>>>>> --Matt
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <[EMAIL PROTECTED]
>>
Chris K Wensel
[EMAIL PROTECTED]
http://concurrentinc.com