Return-Path: X-Original-To: apmail-phoenix-dev-archive@minotaur.apache.org Delivered-To: apmail-phoenix-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 715FB18443 for ; Wed, 6 Apr 2016 23:37:28 +0000 (UTC) Received: (qmail 49645 invoked by uid 500); 6 Apr 2016 23:37:28 -0000 Delivered-To: apmail-phoenix-dev-archive@phoenix.apache.org Received: (qmail 49576 invoked by uid 500); 6 Apr 2016 23:37:28 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 49565 invoked by uid 99); 6 Apr 2016 23:37:28 -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; Wed, 06 Apr 2016 23:37:28 +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 E0226C0C87 for ; Wed, 6 Apr 2016 23:37:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -5.016 X-Spam-Level: X-Spam-Status: No, score=-5.016 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id LlK0l3oWUE_X for ; Wed, 6 Apr 2016 23:37:27 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with SMTP id 6033D5F47D for ; Wed, 6 Apr 2016 23:37:26 +0000 (UTC) Received: (qmail 49330 invoked by uid 99); 6 Apr 2016 23:37:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2016 23:37:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 81F0F2C1F5D for ; Wed, 6 Apr 2016 23:37:25 +0000 (UTC) Date: Wed, 6 Apr 2016 23:37:25 +0000 (UTC) From: "James Taylor (JIRA)" To: dev@phoenix.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229347#comment-15229347 ] James Taylor commented on PHOENIX-2535: --------------------------------------- I don't think we need {{client-without-hbase}} and {{client-minimal}} jars any longer, especially given the shading you're doing. Any opinions, [~tdsilva] or [~mujtabachohan]? > Create shaded clients (thin + thick) > ------------------------------------- > > Key: PHOENIX-2535 > URL: https://issues.apache.org/jira/browse/PHOENIX-2535 > Project: Phoenix > Issue Type: Bug > Reporter: Enis Soztutar > Assignee: Sergey Soldatov > Fix For: 4.8.0 > > Attachments: PHOENIX-2535-1.patch, PHOENIX-2535-2.patch, PHOENIX-2535-3.patch, PHOENIX-2535-4.patch > > > Having shaded client artifacts helps greatly in minimizing the dependency conflicts at the run time. We are seeing more of Phoenix JDBC client being used in Storm topologies and other settings where guava versions become a problem. > I think we can do a parallel artifact for the thick client with shaded dependencies and also using shaded hbase. For thin client, maybe shading should be the default since it is new? -- This message was sent by Atlassian JIRA (v6.3.4#6332)