Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8C4DC7664 for ; Fri, 30 Sep 2011 18:44:31 +0000 (UTC) Received: (qmail 5256 invoked by uid 500); 30 Sep 2011 18:44:30 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 5214 invoked by uid 500); 30 Sep 2011 18:44:30 -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 5205 invoked by uid 99); 30 Sep 2011 18:44:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Sep 2011 18:44:30 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shaposhnik@gmail.com designates 209.85.214.48 as permitted sender) Received: from [209.85.214.48] (HELO mail-bw0-f48.google.com) (209.85.214.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Sep 2011 18:44:24 +0000 Received: by bkbzu5 with SMTP id zu5so2778741bkb.35 for ; Fri, 30 Sep 2011 11:44:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Fc/7Z/rJg/FAybcg4+G8gyddK04MJVn3rwlnKSn1rjI=; b=iUOXw88VAXO2r3+a26UjUHpFSLzkdr9ITkfczHfgmOWleP/oeEIyPpR9ACqNiXHcfa Hl0/hLxm0/UJnE6DWgZ9RE+9Cy479Er/s5Vo9N/IeT5zGetU3dd5vPdkdI9e0p2ikSw6 u7GM3nwezWJA/l0ivtjNxrfb6a8gDsKbAiSws= MIME-Version: 1.0 Received: by 10.204.155.145 with SMTP id s17mr7535266bkw.207.1317408243509; Fri, 30 Sep 2011 11:44:03 -0700 (PDT) Sender: shaposhnik@gmail.com Received: by 10.204.76.2 with HTTP; Fri, 30 Sep 2011 11:44:03 -0700 (PDT) In-Reply-To: <8F4138FC-449A-413C-9A9C-273B5CC7A647@hortonworks.com> References: <7B10DC9F-982F-43ED-9A28-F6C7BE47EA35@hortonworks.com> <363C7E2A-25B6-4828-9ABE-34E9780D476D@hortonworks.com> <4E84E56D.2010503@apache.org> <5388141F-213D-4842-8F36-42D37FE622A4@hortonworks.com> <4E859730.7020306@apache.org> <8F4138FC-449A-413C-9A9C-273B5CC7A647@hortonworks.com> Date: Fri, 30 Sep 2011 11:44:03 -0700 X-Google-Sender-Auth: gY3QrNnGTdIcfw4S0fbLWbyexiI Message-ID: Subject: Re: Update on hadoop-0.23 From: Roman Shaposhnik To: general@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi Arun! On Fri, Sep 30, 2011 at 10:54 AM, Arun C Murthy wrote: > I'm all for people working on what they are passionate about, so this isn't to say one shouldn't spend time on 0.22. > > But, for clarity's sake, as I've done multiple times on both the list and in person to Konstantin etc., > I'll point out (again) that 0.22 will need multiple man-years of development to achieve parity with > 0.20.2xx just in terms of bug-fixes and performance. I apologize if my level of institutional knowledge of these things is lacking, but do you have any benchmarking results between 0.22 and 0.20.2xx? The reason I'm asking is twofold -- I really would like to see an objective numbers qualifying the viability of 0.22 from the performance stand point, but more importantly I would really like to include the benchmarking code into Bigtop. In terms of bugs -- same question. Is there any publicly available list of, at least, the critical ones that make 0.22 not viable from your point of view? Thanks, Roman.