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 6286E200CC7 for ; Sun, 2 Jul 2017 05:17:20 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 54376160BF8; Sun, 2 Jul 2017 03:17:20 +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 749B6160BEA for ; Sun, 2 Jul 2017 05:17:19 +0200 (CEST) Received: (qmail 41923 invoked by uid 500); 2 Jul 2017 03:17:12 -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 41911 invoked by uid 99); 2 Jul 2017 03:17:09 -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; Sun, 02 Jul 2017 03:17:09 +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 0D4D31A049D for ; Sun, 2 Jul 2017 03:17:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.662 X-Spam-Level: * X-Spam-Status: No, score=1.662 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd2-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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id ETAQsGKla8vM for ; Sun, 2 Jul 2017 03:17:06 +0000 (UTC) Received: from mail-vk0-f43.google.com (mail-vk0-f43.google.com [209.85.213.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 92D885F46F for ; Sun, 2 Jul 2017 03:17:06 +0000 (UTC) Received: by mail-vk0-f43.google.com with SMTP id r126so82686647vkg.0 for ; Sat, 01 Jul 2017 20:17:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=l5TDd3WW6Y0iChVysbwINWdSdSL1C7OJeBpLWZn7GRk=; b=Q7plT2BolYh8XBnfinxTTNV5p4cn6iRMAD/TnllVEG3xPtnGmCnIT3o4B7k5OHEXDm t4VS8tj6/0+ARdRVPzm1BPFPOxiDiRBF3uSo6c1VDKjUj65C3rf0X4MH1ARqgF4qmZg0 SSSrKVQXTo7LLmjPb3rGqrmVefmQCGXAEeqeMEASV7hVf0jXhCfC2VpALYo+DIhVmyxG cCoAoiVHOBTVw6lKe2Hcuyjn+xc6QxqlaA5gh2Dw1JXJfXeGwpS0NujAvvvu3mBg/99c cMf1sWG1l67jDt/Yy6wMuLjoq8yd8ulEw27V1PZW4f7oLjn7HeKrCryQjCJETWeOWzZ1 +xHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=l5TDd3WW6Y0iChVysbwINWdSdSL1C7OJeBpLWZn7GRk=; b=pCdrtEKHrKntbM3v7DXmLhPKPqudw9yoqtM+tPjFtvr+6bPLcKI3Dj++aQI73PB0H2 B2uQBMXZ3YUdnOBxSNxjsP8Mn1EkpBQv6KVcpydkToiDGdpABz5mbQ2jqPGYCxyMRsBL 5OADb993fAyK2o5l4EPGpLyIwZW8PBTp8v9YywnwDEajFcjC85QIFqxLeJktEwBNhZfE +zbohKyRiSmX7rEAn3Y+5C2RhFtYGgiiQah3LCls6QRsDKJTpOYyC+nY4W6h/XUorGt6 IXlYesTUBiwCXkgNYcruYiDrbeZQi9AJiErKdNaPeBIj4zGG6kbInkCTuR/jOu7vOml9 7GsA== X-Gm-Message-State: AKS2vOxsBEjEEI8hHzPZbWt7oHUnZaM5Wm9prvrquKn9V1C+ScDR9HUJ 0pH9Z+5tEMpuRPRz7eh3X5d+hHDNr9bgj5Y= X-Received: by 10.31.54.140 with SMTP id d134mr13265179vka.15.1498965420195; Sat, 01 Jul 2017 20:17:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.3.162 with HTTP; Sat, 1 Jul 2017 20:16:59 -0700 (PDT) In-Reply-To: References: From: =?UTF-8?B?5byg6ZOOKER1byBaaGFuZyk=?= Date: Sun, 2 Jul 2017 11:16:59 +0800 Message-ID: Subject: Re: [VOTE] hbase-thirdparty project, first release candidate 1.0.0RC0 To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary="001a1143b52266c33405534d15e7" archived-at: Sun, 02 Jul 2017 03:17:20 -0000 --001a1143b52266c33405534d15e7 Content-Type: text/plain; charset="UTF-8" +1 (binding) Checked sums and signatures: OK 'mvn clean install': OK, the size of the generated jar files are reasonable Unzip the generated jar files: OK, all classes are relocated under org/apache/hadoop/hbase/shaded Only one minor question, seems we do not generate sources jars? There is a hbase-shaded-protobuf-1.0.0-sources.jar after 'mvn install' but the size is only 22 bytes. Thanks. 2017-07-02 2:38 GMT+08:00 Stack : > +1 from me. > St.Ack > > On Fri, Jun 30, 2017 at 3:07 PM, Stack wrote: > > > This is an interesting vote. The vote is on an RC made out of a new hbase > > project, hbase-thirdparty. > > > > First the usual stuff. > > > > The 1.0.0RC0 is available at: > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty/1.0.0RC0/ > > > > Maven artifacts are in the following staging repository: > > > > https://repository.apache.org/content/repositories/orgapachehbase-1171 > > > > Artifacts are signed with 8ACC93D2 which is at the tail of our KEYS file > > http://www-us.apache.org/dist/hbase/KEYS. > > > > I tagged this RC as 1.0.0RC at 8ffaf3dd561052bcc71772148ecd04cdf9e224f3 > > in the new hbase-thirdparty repository at [1]. > > > > Now to the unusual. > > > > The artifact was made from a new repository, hbase-thirdparty[1]. > > hbase-thirdparty is a project overseen by the hbase PMC. It came of > > discussion on the dev list in the thread '[DISCUSS] More Shading' [2]. > > Its charge is the hosting of ornery thirdparty libs -- e.g. protobuf, > > guava, netty -- that need patching and/or shading so we are no longer > bound > > by whatever the version of a lib Hadoop happens to ship (and we can > change > > versions w/o damaging out glorious downstreamers). In the past, when > we've > > been able, we've done this dirty patching and shading work as an > > unacknowledged 'pre-build' hack step appended to our protobuf file > > generation. Moving this mess out of our mainline build to live elsewhere, > > pulled in as a legit 'dependency', simplifies our build particularly > around > > the shading of third-part libs; the narrower scope of a dedicated project > > that produces transformed jars is easier to reason about, is less likely > to > > clash with existing dependencies whether transitive or otherwise, and it > > makes for less spaghetti poms. > > > > Other (minor) benefits include our being able to generate protobuf files > > inline now; no need of the pre-build anymore nor checking in of generated > > protobuf files (25MB). There is a patch to remove them (predicated on > this > > hbase-thirdparty release): "HBASE-17056 Remove checked in PB generated > > files". > > > > Downside is having to explicitly reference our version in code as in > > org.apache.hadoop.hbase.shaded.com.google.protobuf.Message rather than > > just com.google.protobuf.Message and so on for guava references, etc. > > (We've been doing this for a while now so hopefully it not too strange > > developing)*. > > > > There is little to this new project other than a few poms to do packaging > > and a couple of patches we apply on build. It works by pulling down > > dependencies and doing whatever shading, renaming, or patching we need. > > Currently hbase-thirdparty hosts protobuf (3.1.0 => 3.3.1), guava (12.0 > => > > 22.0), gson, protobuf-util, and netty 4.1.12-FINAL. It publishes three > jars > > for hbase to consume: hbase-shaded-protobuf, hbase-shaded-netty, and then > > hbase-shaded-miscellaneous for the remaining libs. Philosophy is if the > lib > > is troublesome, protobuf needs patching and netty includes an .so that > > needs a rename, then give it its own module (See README in the release > for > > more). I've arrived at this layout for hbase-thirdparty after a bunch of > > experimentation and messing with hbase dependencies (See sub-tasks under > > HBASE-17898 Update dependencies). That said, as we head to hbase-2.0.0, > we > > might have to make a an odd new release of hbase-thirdparty but > thereafter > > I'd imagine it should settle down to be an infrequent update. > > > > VOTE lasts 72 hours. Let +1 be an assent to the hbase-thirdparty project > > and a vote for this RC. > > > > Questions on how it will go w/ this project welcome on this thread. If > > heavy-detail on how the shading works, I suggest ask on the '[DISCUSS] > More > > Shading' thread. > > > > Thanks, > > St.Ack > > 1. https://git-wip-us.apache.org/repos/asf/hbase-thirdparty > > 2. See the '[DISCUSS] More Shading' thread, > http://apache-hbase.679495.n3. > > nabble.com/DISCUSS-More-Shading-td4083025.html > > > > * Doc on how to make use of hbase-thirdparty is coming for the refguide. > > > > > > > --001a1143b52266c33405534d15e7--