I was reading the Hadoop Next Generation post on the YDN by Arun
(http://developer.yahoo.com/blogs/hadoop/posts/2011/02/mapreduce-nextgen/),
and
I was wondering if this development is public and where I can find the
sources for this?
Regards and thanks a lot for reading
--
Marcos Luís Ortíz
On 06/13/2011 09:01 AM, Harsh J wrote:
Right now, its in the public SVN branch of MapReduce named MR-279.
See https://issues.apache.org/jira/browse/MAPREDUCE-279, which is its
giant umbrella ticket. It may be merging into trunk (0.23) sometime
soon in the future, though.
On Mon, Jun 13, 2011
0.23 is trunk right now. 0.22 was branched for stabilization before release.
--Bobby
On 6/13/11 9:14 AM, Marcos Ortiz mlor...@uci.cu wrote:
On 06/13/2011 09:01 AM, Harsh J wrote:
Right now, its in the public SVN branch of MapReduce named MR-279.
See
Hey Robert,
It seems to be working for me... what URL are you trying to check out?
I moved aside my ~/.subversion dir, and then did:
$ svn co http://svn.apache.org/repos/asf/hadoop/common/branches/MR-279/
Thanks
-Todd
On Mon, Jun 13, 2011 at 7:05 AM, Robert Evans ev...@yahoo-inc.com wrote:
Hmm, as I got farther down my email this morning, I saw some complaints that
HBase's SVN was giving 403s as well, this morning. Perhaps there is some
ASF-wide issue going on, completely unrelated to the Hadoop changes over the
weekend?
-Todd
On Mon, Jun 13, 2011 at 7:52 AM, Todd Lipcon
When I checkout the yahoo-merge branch, I see these svn externals warnings:
svn: warning: Error handling externals definition for
'yahoo-merge/hdfs/src/test/bin':
svn: warning: URL
'https://svn.apache.org/repos/asf/hadoop/common/trunk/src/test/bin' at
revision 1135120 doesn't exist
svn: warning:
Todd,
It seems to be working now, so whatever it was it is now gone.
--Bobby
On 6/13/11 9:57 AM, Todd Lipcon t...@cloudera.com wrote:
Hmm, as I got farther down my email this morning, I saw some complaints that
HBase's SVN was giving 403s as well, this morning. Perhaps there is some
ASF-wide
Yes, many thanks for carrying this over the finish line!
Cheers,
Nige
Sent from my iPhone4
On Jun 13, 2011, at 12:39 AM, Eli Collins e...@cloudera.com wrote:
Nice work Todd. Thank you for making this happen!
On Sun, Jun 12, 2011 at 4:38 PM, Todd Lipcon t...@cloudera.com wrote:
OK,
On Mon, Jun 13, 2011 at 8:14 AM, Todd Lipcon t...@cloudera.com wrote:
Oops, sorry about that one. I will take care of that in about 30 minutes
(just headed out the door now to catch a train). If someone else with commit
access wants to, you just need to propset the externals to point to th
On Mon, Jun 13, 2011 at 9:24 AM, Jeffrey Naisbitt jnais...@yahoo-inc.comwrote:
As you say though, I would think it should still work with three separate
projects, so I'll just go back to that for now. It would be nice to be
able
to build the whole thing as a single project though (since it's
I tend to agree: JIRA separation was the benefit of the split.
I'd rather keep the current JIRA split in effect (e.g. separate JIRA projects
for separate Hadoop components; don't recombine them) and file patches in the
same way (for common, hdfs, mapreduce). If a cross component patch is needed
Todd, it's so great to have this done. Thanks for the huge amount of hard work!
--Matt
On Jun 13, 2011, at 10:08 AM, Jeffrey Naisbitt wrote:
On 6/13/11 12:01 PM, Todd Lipcon t...@cloudera.com wrote:
On Mon, Jun 13, 2011 at 9:24 AM, Jeffrey Naisbitt
jnais...@yahoo-inc.comwrote:
As you say
On Mon, Jun 13, 2011 at 11:42 AM, Tsz Wo (Nicholas), Sze
s29752-hadoopgene...@yahoo.com wrote:
Todd,
Great work!
A few minor problems:
(1) I had committed MAPREDUCE-2588, however, an commit email was sent to
both
common-commits@ and mapreduce-commits@.
(2) hadoop/site becomes an empty
On Mon, Jun 13, 2011 at 01:37PM, Todd Lipcon wrote:
On Mon, Jun 13, 2011 at 11:51 AM, Konstantin Boudnik c...@apache.org wrote:
I tend to agree: JIRA separation was the benefit of the split.
I'd rather keep the current JIRA split in effect (e.g. separate JIRA
projects
for separate
On Mon, Jun 13, 2011 at 4:54 PM, Konstantin Boudnik c...@apache.org wrote:
On Mon, Jun 13, 2011 at 01:37PM, Todd Lipcon wrote:
On Mon, Jun 13, 2011 at 11:51 AM, Konstantin Boudnik c...@apache.org
wrote:
I tend to agree: JIRA separation was the benefit of the split.
I'd rather keep
15 matches
Mail list logo
