Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 2 May 2016 21:55:12 +0000 (UTC)
From: "Nick Dimiduk (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12964415.1462216741000.90751.1462226112865@Atlassian.JIRA>
In-Reply-To: <JIRA.12964415.1462216741000@Atlassian.JIRA>
References: <JIRA.12964415.1462216741000@Atlassian.JIRA> <JIRA.12964415.1462216741065@arcas>
Subject: [jira] [Commented] (HBASE-15749) Shade guava dependency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 02 May 2016 21:55:19 -0000


    [ https://issues.apache.org/jira/browse/HBASE-15749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267581#comment-15267581 ] 

Nick Dimiduk commented on HBASE-15749:
--------------------------------------

We need to get to a place where we only ship a thoroughly shaded client. Don't make downstreamers adapt to our crazy hadoop dependencies. I've burned a lot of time on this problem up and down the stack over the last couple months; I'm convinced this is the only way forward.

bq. I don't understand what this issue is proposing.

Agreed, context would be helpful. I don't think we want to be in the business of partial shading here, full shading there.

> Shade guava dependency
> ----------------------
>
>                 Key: HBASE-15749
>                 URL: https://issues.apache.org/jira/browse/HBASE-15749
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>
> HBase codebase uses Guava library extensively.
> There have been JIRAs such as HBASE-14963 which tried to make compatibility story around Guava better.
> Long term fix, as suggested over in HBASE-14963, is to shade Guava dependency.
> Future use of Guava in HBase would be more secure once shading is done.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)