hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-15749) Shade guava dependency
Date Mon, 02 May 2016 23:45:13 GMT

     [ https://issues.apache.org/jira/browse/HBASE-15749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-15749.
---------------------------
    Resolution: Not A Problem

Resolving as not a problem.

We got here because HBASE-15737 had StopWatch in hbase-server as a 'problem'. Attempts at
eliciting why it a problem got "Our codebase should be consistent w.r.t. the usage of stop
watch" and "... reduce the chance of incompatibilities in case newer version of Guava is involved",
and so on.

HBASE-15737 seems to have been prompted by HBASE-14963 where suggestions of shaded client
didn't carry because version concerned was older -- pre-shaded-client. HBASE-14963 included
suggestion of shading guava that was repeated by me in HBASE-15737 when in this later context
I should have talked up shaded modules instead.







> 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)

Mime
View raw message