Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D4659107 for ; Mon, 13 Feb 2012 21:19:22 +0000 (UTC) Received: (qmail 62759 invoked by uid 500); 13 Feb 2012 21:19:21 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 62584 invoked by uid 500); 13 Feb 2012 21:19:21 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 62565 invoked by uid 99); 13 Feb 2012 21:19:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2012 21:19:20 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com designates 74.125.82.169 as permitted sender) Received: from [74.125.82.169] (HELO mail-we0-f169.google.com) (74.125.82.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2012 21:19:15 +0000 Received: by wera13 with SMTP id a13so4908005wer.14 for ; Mon, 13 Feb 2012 13:18:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Y+yazPvHyFvTs0jSOzyiGkPw5V+2PFXGAqIqSV6vTc8=; b=M0QerLIUVPYkKzj5QBHj5b16O+QEZeytyLHQBxzg1O89LABwoPDSfVte/TWDxYmsZT SdrkK5IXJez9jrRYvfR3RoijudRfZa1A/2V9icRhYpsx8z83/3GNnZcLX3kQRkcFnGur O4XjKz+hXy9ujy/9vXVdCyEYqFa7gm48aLl4U= MIME-Version: 1.0 Received: by 10.180.89.71 with SMTP id bm7mr20482439wib.20.1329167934688; Mon, 13 Feb 2012 13:18:54 -0800 (PST) Received: by 10.216.166.72 with HTTP; Mon, 13 Feb 2012 13:18:54 -0800 (PST) In-Reply-To: References: Date: Mon, 13 Feb 2012 13:18:54 -0800 Message-ID: Subject: Re: HBase wire compatibility From: Ted Yu To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=f46d04447e0b980cfa04b8df065f --f46d04447e0b980cfa04b8df065f Content-Type: text/plain; charset=ISO-8859-1 What's the role of HBASE-5306 in your proposal ? Thanks On Mon, Feb 13, 2012 at 1:02 PM, Jimmy Xiang wrote: > I posted the proposal on wiki: > > http://wiki.apache.org/hadoop/Hbase/HBaseWireCompatibility > > Thanks, > Jimmy > > On Mon, Feb 13, 2012 at 11:03 AM, Ted Yu wrote: > > > Can you post on wiki ? > > > > Attachment stripped. > > > > On Mon, Feb 13, 2012 at 11:01 AM, Jimmy Xiang > wrote: > > > > > Hello, > > > > > > As HBase installation base is getting bigger, we are ready to work on > the > > > wire compatibility issue. > > > The goal is to make HBase easier for operators to upgrade, while it is > > > also easier for developers to > > > enhance, re-architect if necessary. > > > > > > The attached is a proposal we came up. We'd like to start with two > > phases: > > > > > > Phase 1: Compatibility between client applications and HBase clusters > > > Phase 2: HBase cluster rolling upgrade within same major version > > > > > > Could you please review? > > > > > > Thanks, > > > Jimmy > > > > > > --f46d04447e0b980cfa04b8df065f--