Return-Path: Delivered-To: apmail-hadoop-general-archive@locus.apache.org Received: (qmail 76413 invoked from network); 6 Aug 2008 05:39:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Aug 2008 05:39:15 -0000 Received: (qmail 77046 invoked by uid 500); 6 Aug 2008 05:39:15 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 76987 invoked by uid 500); 6 Aug 2008 05:39:15 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 76976 invoked by uid 99); 6 Aug 2008 05:39:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Aug 2008 22:39:15 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dhruba@gmail.com designates 209.85.128.190 as permitted sender) Received: from [209.85.128.190] (HELO fk-out-0910.google.com) (209.85.128.190) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Aug 2008 05:38:19 +0000 Received: by fk-out-0910.google.com with SMTP id 26so2559383fkx.13 for ; Tue, 05 Aug 2008 22:38:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=5YYa7WGd4hbkN5lpq6Tcmbvc/j1069+Jjl6Eiw4rXV0=; b=BHPwzA8uRSbbaFSUzenrHZdFpu8rRAP+BXaZvK2nmktiWp3e6svNk8c3ZMxYwhQQy4 ywB+oBK9wO2mL7r9OiXt098+GZ7D19RcwGgRaLXNgGqZupIslh8rOfpzMwS+r3bVc8oQ QFFt/z5dgmsJO4zbbxJEvUR1sLfD7KeVRFCro= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=krKX9E3bNIFOlbyM+3L4anpegme9zPCzOXss1dAtbox/vLJFok2Kd7NZk3NhmenjJE BHonO7X0rhqCsE/Hiu6tOfGOlESOElzK0J/2bKs8fxDjpukN44xRMNisrugYbKjaba5H Q/4CuG0syCz2WyHx85cjXsWE4aEZrs931C2IA= Received: by 10.125.87.8 with SMTP id p8mr101867mkl.80.1218001125082; Tue, 05 Aug 2008 22:38:45 -0700 (PDT) Received: by 10.125.145.7 with HTTP; Tue, 5 Aug 2008 22:38:45 -0700 (PDT) Message-ID: <4aa34eb70808052238sb272613v6766a69b76537c33@mail.gmail.com> Date: Tue, 5 Aug 2008 21:38:45 -0800 From: "Dhruba Borthakur" To: general@hadoop.apache.org Subject: Re: [VOTE] Should we create sub-projects for HDFS and Map/Reduce? In-Reply-To: <688CEB2A-13EF-4C38-855A-3D6D4C3485B3@yahoo-inc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <688CEB2A-13EF-4C38-855A-3D6D4C3485B3@yahoo-inc.com> X-Virus-Checked: Checked by ClamAV on apache.org Are you talking about sub-projects for core, hdfs and mapreduce? Or is there another way to allow for having separate mailing lists/jiras for these components? I had liked the fact that these pieces are together. It makes the code compile together, keeps API upgradation simple and enhances developer community building across all these three pieces of code. Actually, JIRAs have their own components and we can always filter them using their component, can't we? thanks, dhruba On Tue, Aug 5, 2008 at 9:18 PM, Owen O'Malley wrote: > I think the time has come to split Hadoop Core into three pieces: > > 1. Core (src/core) > 2. HDFS (src/hdfs) > 3. Map/Reduce (src/mapred) > > There will be lots of details to work out, such as what we do with tools and > contrib, but I think it is a good idea. This will create separate jiras and > mailing lists for HDFS and map/reduce, which will make the community much > more approachable. I would propose that we wait until 0.19.0 is released to > give us time to plan the split. > > -- Owen >