Return-Path: 
 <common-dev-return-72680-apmail-hadoop-common-dev-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org
Received: (qmail 11994 invoked from network); 25 Sep 2009 19:51:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 25 Sep 2009 19:51:12 -0000
Received: (qmail 58984 invoked by uid 500); 25 Sep 2009 19:51:11 -0000
Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org
Received: (qmail 58907 invoked by uid 500); 25 Sep 2009 19:51:11 -0000
Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-dev@hadoop.apache.org>
List-Id: <common-dev.hadoop.apache.org>
Reply-To: common-dev@hadoop.apache.org
Delivered-To: mailing list common-dev@hadoop.apache.org
Received: (qmail 58897 invoked by uid 99); 25 Sep 2009 19:51:11 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Sep 2009 19:51:11 +0000
X-ASF-Spam-Status: No, hits=-4.0 required=10.0
	tests=RCVD_IN_DNSWL_MED,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of awittenauer@linkedin.com
 designates 69.28.149.24 as permitted sender)
Received: from [69.28.149.24] (HELO esv4-mav02.corp.linkedin.com)
 (69.28.149.24)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Sep 2009 19:51:01 +0000
DomainKey-Signature: s=prod; d=linkedin.com; c=nofws; q=dns;
  h=X-IronPort-AV:Received:User-Agent:Date:Subject:From:To:
   Message-ID:Thread-Topic:Thread-Index:In-Reply-To:
   Mime-version:Content-type:Content-transfer-encoding;
  b=QqHgjLMInyO1hrlamkOwhauuIEE36x/xoazD73zc1GDxp9YhdwwhXgZB
   McRsE+6afLNx2gGyP2hfcQVkmdiCT4F5pWS+ByZhUg3nPdKBBmiEnkep1
   iqsX/cYg8SRPucX;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
  d=linkedin.com; i=awittenauer@linkedin.com; q=dns/txt;
  s=proddkim; t=1253908261; x=1285444261;
  h=from:sender:reply-to:subject:date:message-id:to:cc:
   mime-version:content-transfer-encoding:content-id:
   content-description:resent-date:resent-from:resent-sender:
   resent-to:resent-cc:resent-message-id:in-reply-to:
   references:list-id:list-help:list-unsubscribe:
   list-subscribe:list-post:list-owner:list-archive;
  z=From:=20Allen=20Wittenauer=20<awittenauer@linkedin.com>
   |Subject:=20Re:=20Towards=20Hadoop=201.0:=20Stronger=20AP
   I=20Compatibility=20from=200.21=20onwards|Date:=20Fri,=20
   25=20Sep=202009=2012:50:00=20-0700|Message-ID:=20<C6E26CF
   8.863%awittenauer@linkedin.com>|To:=20<common-dev@hadoop.
   apache.org>|Mime-version:=201.0
   |Content-transfer-encoding:=207bit|In-Reply-To:=20<E1B2B6
   A3-B446-41D8-85E3-1BB7E8934A87@yahoo-inc.com>;
  bh=qc6Aq2n1CjXgvpdKDB+tFhPBm+tzAkHc/tAQTuQrZuw=;
  b=NaOfrP+t7JsS9PtJf8c1Zdovhp4JPOp4h5j0E3B1u/BIG41h6y+cjPCt
   HxfBueuyl2WI66ugMFZzaYH08Ta496TnqM6a1c0n/ErnvB4P5uBbtaFzL
   zmqmYUG0ougwq9X;
X-IronPort-AV: E=Sophos;i="4.44,453,1249282800";
   d="scan'208";a="9015004"
Received: from 172.16.19.135 ([172.16.19.135]) by CORP-MAIL.linkedin.biz
 ([172.18.46.135]) via Exchange Front-End Server mail-access.linkedin.biz
 ([172.18.46.133]) with Microsoft Exchange Server HTTP-DAV ;
 Fri, 25 Sep 2009 19:50:01 +0000
User-Agent: Microsoft-Entourage/12.10.0.080409
Date: Fri, 25 Sep 2009 12:50:00 -0700
Subject: Re: Towards Hadoop 1.0: Stronger API Compatibility from 0.21 onwards
From: Allen Wittenauer <awittenauer@linkedin.com>
To: <common-dev@hadoop.apache.org>
Message-ID: <C6E26CF8.863%awittenauer@linkedin.com>
Thread-Topic: Towards Hadoop 1.0: Stronger API Compatibility from 0.21 onwards
Thread-Index: Aco+GV2p5xrTo3oa2EK/iCghGPeCTw==
In-Reply-To: <E1B2B6A3-B446-41D8-85E3-1BB7E8934A87@yahoo-inc.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org




On 9/25/09 12:44 PM, "Sanjay Radia" <sradia@yahoo-inc.com> wrote:

> 
> On Sep 25, 2009, at 12:03 PM, Allen Wittenauer wrote:
> 
>> On 9/25/09 10:13 AM, "Dhruba Borthakur" <dhruba@gmail.com> wrote:
>>> It is really nice to have wire-compatibility between clients and
>> servers
>>> running different versions of hadoop. The reason we would like
>> this is
>>> because we can allow the same client (Hive, etc) submit jobs to two
>>> different clusters running different versions of hadoop. But I am
>> not stuck
>>> up on the name of the release that supports wire-compatibility, it
>> can be
>>> either 1.0  or something later than that.
>> 
>> To me, the lack of wire compatibility makes will make "Hadoop 1.0"
>> in name
>> only when in reality it is more like 0.80. :(
> 
> My sentiments exactly, though I could learn to live with it ....

We just had this discussion today about how to put Hadoop into a production
pipeline.  I was under the impression that 1.0 was going to be wire
compatible too.

This is just so disappointing and, quite frankly, makes 1.0 less than useful
for Real Work.  Great, the APIs don't  change but you still have the same
problems of getting data on/off the grid without upgrading your clients
every time. 

To me, without wire compatibility, 1.0 makes me feel pretty "meh; who
cares--we're still going to be in upgrade hell".