From user-return-55394-archive-asf-public=cust-asf.ponee.io@hbase.apache.org Thu Jul 26 07:55:15 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1CCD5180621 for ; Thu, 26 Jul 2018 07:55:14 +0200 (CEST) Received: (qmail 34087 invoked by uid 500); 26 Jul 2018 05:55:13 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 34059 invoked by uid 99); 26 Jul 2018 05:55:12 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jul 2018 05:55:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D37A31A0811; Thu, 26 Jul 2018 05:55:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.749 X-Spam-Level: ** X-Spam-Status: No, score=2.749 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=2, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id PKveUaUbp5wd; Thu, 26 Jul 2018 05:55:10 +0000 (UTC) Received: from mail-pl0-f50.google.com (mail-pl0-f50.google.com [209.85.160.50]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id A4E605F402; Thu, 26 Jul 2018 05:55:09 +0000 (UTC) Received: by mail-pl0-f50.google.com with SMTP id t17-v6so305030ply.13; Wed, 25 Jul 2018 22:55:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1hn3HJoJc2/8YX8uHlju1DKg0zjh1zv1QG1wA7IrUu0=; b=BFM0tuaPqrv/nuGDbbjvVgpcU8thAWiu7IBDXe+86iLCT244R+UmM1eaoUVbbFsVMf jn0PQqfK/FDHecEKzJ9bZP0iXhlHqSuti6HLkym4e3th0ZX587gzhixhivIPq1U2Jw/6 JFLyus/ePMY3KkKaZy9WvE42LjscVSCu/hKKjYKIllZMD5jWATlar0dtLSBi9NDeyTW6 xneIeBuhUWIr5uB91snXU9KmJc5PX/VFPrKKDFsKWz9xgwIihVHZk4L1dFZZ/qDdLEmB FMLNV6vFDU14yc9LQLkThG+XCFzCNb7pZInGWox5A+J6V/kSuE55vfK2RT7JiTh0H+D/ zxtg== X-Gm-Message-State: AOUpUlF6UM9CgKQ7XfuZWafBZepnXF3NfHKQwXs/6mt1dLyQDWWAXJGE uNaOeudpcqg1SpYKcIFzBZD8gzjLeGG0z0l1bZOMjA== X-Google-Smtp-Source: AAOMgpcDa0EqFcxg4GprREA5puXkABgynMTUzB/uSXrdvjxc8+Oq3/Em0aaYB77MHC76mbeMvO4mBNvDvowL2ILIWEA= X-Received: by 2002:a17:902:740a:: with SMTP id g10-v6mr642392pll.204.1532584507851; Wed, 25 Jul 2018 22:55:07 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Stack Date: Wed, 25 Jul 2018 22:54:56 -0700 Message-ID: Subject: Re: [DISCUSS] Separate Git Repository for HBCK2 To: HBase Dev List Cc: Hbase-User Content-Type: multipart/alternative; boundary="0000000000002dc8050571e0a3f0" --0000000000002dc8050571e0a3f0 Content-Type: text/plain; charset="UTF-8" On Tue, Jul 24, 2018 at 10:27 AM Andrew Purtell wrote: > If we do this can we also move out hbck version 1? It would be really weird > in my opinion to have v2 in a separate repo but v1 shipping with the 1.x > releases. That would be a source of understandable confusion. > > My sense is that hbck1 is not externalizable; we'd not be able to move it out of core because it does dirty tricks all over the shop. But lets see... S > I believe our compatibility guidelines allow us to upgrade interface > annotations from private to LP or Public and from LP to Public. These are > not changes that impact source or binary compatibility. They only change > the promises we make going forward about their stability. I believe we can > allow these in new minors, so we could potentially move hbck out in a > 1.5.0. > > > On Mon, Jul 23, 2018 at 4:46 PM Stack wrote: > > > On Thu, Jul 19, 2018 at 2:09 PM Umesh Agashe > > > > > wrote: > > > > > Hi, > > > > > > I've had the opportunity to talk about HBCK2 with a few of you. One of > > the > > > suggestions is to to have a separate git repository for HBCK2. Lets > > discuss > > > about it. > > > > > > In the past when bugs were found in hbck, there is no easy way to > release > > > patched version of just hbck (without patching HBase). If HBCK2 has a > > > separate git repo, HBCK2 versions will not be tightly related to HBase > > > versions. Fixing and releasing hbck2, may not require patching HBase. > > > Though tight coupling will be somewhat loosened, HBCK2 will still > depend > > on > > > HBase APIs/ code. Caution will be required going forward regarding > > > compatibility. > > > > > > What you all think? > > > > > > > > I think this the way to go. > > > > We'd make a new hbase-hbck2 repo as we did for hbase-thirdparty? > > > > We'd use the hbase JIRA for hbase-hbck2 issues? > > > > We'd make hbase-hbck2 releases on occasion that the PMC voted on? > > > > Sounds great! > > St.Ack > > > > Thanks, > > > Umesh > > > > > > JIRA: https://issues.apache.org/jira/browse/HBASE-19121. > > > Doc: > > > > > > > > > https://docs.google.com/document/d/1NxSFu4TKQ6lY-9J5qsCcJb9kZOnkfX66KMYsiVxBy0Y/edit?usp=sharing > > > > > > > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands > - A23, Crosstalk > --0000000000002dc8050571e0a3f0--