Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 59535200D3C for ; Tue, 31 Oct 2017 05:36:17 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 57FEE160BF8; Tue, 31 Oct 2017 04:36:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9A464160BE4 for ; Tue, 31 Oct 2017 05:36:16 +0100 (CET) Received: (qmail 22288 invoked by uid 500); 31 Oct 2017 04:36:15 -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 22276 invoked by uid 99); 31 Oct 2017 04:36:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Oct 2017 04:36:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 71C2ACF27D for ; Tue, 31 Oct 2017 04:36:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.98 X-Spam-Level: * X-Spam-Status: No, score=1.98 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id pQ1Zp4v6VshR for ; Tue, 31 Oct 2017 04:36:12 +0000 (UTC) Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 1B3CB61170 for ; Tue, 31 Oct 2017 04:36:12 +0000 (UTC) Received: by mail-wm0-f45.google.com with SMTP id m72so19807479wmc.1 for ; Mon, 30 Oct 2017 21:36:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=wmYhfDwAp4JNjlapabIs+jYXcROq9SrPIlY4x4MLSxs=; b=FtAqnA9PNJZsZf4m+GSnBj4iJ5nsvqrTjMDOv2WH7YqX24TtAJT/cHgtqJgc21thKk 02E2vf2XdBXhu0G74vev09lPiYhqC1P6e+8ADpFBCPWNYEwSCMJMgVLeUaRDPbzrV5l+ BxtEEgoaz9zJkNbJ510Y3wobdERbNayuFALhWwT+ysaviL416N2RNwEJms+EiuRJW5rw Z4K7qFTRH7GAxkff02kNIpVVQiYNC7uYiczp4KGsFUBaqPA+yolspp3aBwdqZLpBB8U2 eyRXs/Iw9yItdnUFrcIZY1eE6jji16/VLwccG/mek5SMzkwS0Mbytt12kBzoFDBBjLWt z5Jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=wmYhfDwAp4JNjlapabIs+jYXcROq9SrPIlY4x4MLSxs=; b=K3x+vQYWGHp7pYEkcDRVdwX2ZoCXBpw5sfQnJoUoErJ/qWecBhetVG5ro6ie1VKVlB ucDEt2GHK4XibRAs8n+PBHMP8P7wxzXehr0WPJNUoqR28Yh94IQ6fE+SWhsQbWgWXbNt vxYXPlFqS3GvEIuVX1TqQmY5qJ+bZPp4kiHskSR7B03ExzGaffGLmcoEr3vhSR4mFIFP pOyor743IiWjGhKj+1RhdvM/47kAnviRLeIHEiCo5/pkP/RhoQhkaOAT8FLKuFqYshUn pTQ976ee31L6UNwvtaGs2DZfWfjOs5pj22+cs/AgpCx15xOaHBPiwHT/wxNIIibwM+pt /l5A== X-Gm-Message-State: AMCzsaW5LV18y2GHqLjzyDdHGQ4oQtURFsLfP52g+MHIwQrDOiem87Me EUwD0ccKNfkLl4wRcC6wPYTvJ/aXmtbFdUCX03CnBQ== X-Google-Smtp-Source: ABhQp+RlYYiuL9XnYDWQ9KyFaH/w1Fl3ZPa3tGAPQxpV1sWT8ngJ57+FhkkTzioOSiUmensQreAS9kE5QrfXP2v7/kk= X-Received: by 10.28.58.81 with SMTP id h78mr719463wma.10.1509424570536; Mon, 30 Oct 2017 21:36:10 -0700 (PDT) MIME-Version: 1.0 Sender: saint.ack@gmail.com Received: by 10.223.161.158 with HTTP; Mon, 30 Oct 2017 21:36:09 -0700 (PDT) In-Reply-To: References: From: Stack Date: Mon, 30 Oct 2017 21:36:09 -0700 X-Google-Sender-Auth: loV6FXF4j7-X91KdgAdH8rcxEOY Message-ID: Subject: Re: [DISCUSS] hbase-2.0.0 compatibility expectations To: HBase Dev List Content-Type: multipart/alternative; boundary="001a1148d708579939055cd04b27" archived-at: Tue, 31 Oct 2017 04:36:17 -0000 --001a1148d708579939055cd04b27 Content-Type: text/plain; charset="UTF-8" On Mon, Oct 30, 2017 at 11:46 AM, Jerry He wrote: > Hi, Stack > > Coming back to this thread, i have meant to ask this question long ago. > Do we support hbase-2 client going against hbase-1 server? > It has not been an objective. It might work doing basic Client API on a later branch-1 but will fail doing Admin functions (and figuring if a Table is online). I've not tried it Jerry. If it was a small thing to make it work, lets get it in. St.Ack > We seem to be fine mix-and-match the clients and servers within the > hbase-1 releases. And IIRC hbase-1 client is ok against 0.98 server. > Suppose I have a product that depends and bundles HBase client. I > want to upgrade the dependency to hbase-2 so that it can take > advantages of and claim support of hbase-2. > But does it mean that I will need drop the claims that the new version > of the product support any hbase-1 backend? > > Thanks. > > > > On Tue, Sep 12, 2017 at 10:21 AM, Stack wrote: > > Let me put this one on this thread, G1GC on by default in hbase2? > > St.Ack > > > > On Wed, Aug 2, 2017 at 4:38 PM, Stack wrote: > > > >> What are our expectations regards compatibility between hbase1 and > hbase2? > >> > >> Lets have a chat about it. Here are some goal posts. > >> > >> + You have to upgrade to hbase-1.x before you can migrate to hbase-2. No > >> migration from < hbase-1 (Is this too onerous? Should we support 0.98 => > >> 2.0?). > >> + You do NOT have to upgrade to the latest release of hbase1 to migrate > to > >> hbase2; being up on hbase-1.0.0+ will be sufficient. > >> + You'll have to update your hbase1 coprocessors to deploy them on > hbase2. > >> A bunch of CP API has/will change by the time hbase2 comes out; e.g. > >> watching for region split on RegionServer no longer makes sense given > >> Master runs all splits now. > >> + An hbase1 client can run against an hbase2 cluster but it will only be > >> able to do DML (Get/Put/Scan, etc.). We do not allow being able to do > admin > >> ops using an hbase1 Admin client against an hbase2 cluster. We have some > >> egregious API violations in branch-1; e.g. we have protobuf in our API > (See > >> HBASE-15607). The notion is that we can't afford a deprecation cycle > >> purging this stuff from our Admin API. > >> > >> What you all think? > >> > >> St.Ack > >> > >> > >> > >> > >> > >> > >> > >> > >> > --001a1148d708579939055cd04b27--