Hello Hadoop Community,
Given the tremendous positive feedback we've all had regarding the HDFS,
MapReduce, and Common project split, I'd like to propose we take the next
step and further separate the existing projects.
I propose we begin by splitting the MapReduce project into separate Map
and
+4.01. This is a terrific idea.
On Fri, Apr 1, 2011 at 1:19 AM, Aaron T. Myers a...@cloudera.com wrote:
Hello Hadoop Community,
Given the tremendous positive feedback we've all had regarding the HDFS,
MapReduce, and Common project split, I'd like to propose we take the next
step and further
Experience developing Hadoop has shown that we not only need to
partition our projects for more active releases, but we also should
explore speculative project splits. For this, a Hadoop.next() project
should track the development of a project scheduler that can partition
the Hadoop subprojects,
-1+2. This could potentially allow us to replace Jenkins with Hadoop for our
build and test infrastructure. That would be awesome!
n.
On Apr 1, 2011, at 1:57 AM, Chris Douglas wrote:
Experience developing Hadoop has shown that we not only need to
partition our projects for more active
+1
This will allow Hadoop to better compete with GoDaddy's Hadoop Killer
skunkworks project.
On Fri, Apr 1, 2011 at 11:26 AM, Nigel Daley nda...@mac.com wrote:
-1+2. This could potentially allow us to replace Jenkins with Hadoop for
our build and test infrastructure. That would be awesome!
LOL@Chris!!!
On Apr 1, 2011, at 1:57 AM, Chris Douglas wrote:
Experience developing Hadoop has shown that we not only need to
partition our projects for more active releases, but we also should
explore speculative project splits. For this, a Hadoop.next() project
should track the development
On Apr 1, 2011, at 12:40 PM, Allen Wittenauer wrote:
On Apr 1, 2011, at 1:57 AM, Chris Douglas wrote:
Experience developing Hadoop has shown that we not only need to
partition our projects for more active releases, but we also should
explore speculative project splits. For this, a
Strong -1 from me, this *idiotic* since we first need to split the NN and DN
into separate projects.
-- amr
On Fri, Apr 1, 2011 at 10:40 AM, Allen Wittenauer
awittena...@linkedin.comwrote:
On Apr 1, 2011, at 1:57 AM, Chris Douglas wrote:
Experience developing Hadoop has shown that we not
On Fri, Apr 1, 2011 at 08:26, Nigel Daley nda...@mac.com wrote:
-1+2. This could potentially allow us to replace Jenkins with Hadoop for our
build and test infrastructure. That would be awesome!
Has anyone checked a calendar lately?
On Apr 1, 2011, at 1:57 AM, Chris Douglas wrote:
And I tend to believe to all sort of stuff on this particular day
because this happens to be my birthday ;(
On Fri, Apr 1, 2011 at 12:35, Allen Wittenauer a...@apache.org wrote:
On Apr 1, 2011, at 11:41 AM, Konstantin Boudnik wrote:
On Fri, Apr 1, 2011 at 08:26, Nigel Daley nda...@mac.com
10 matches
Mail list logo
