hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14963) Remove Guava dependency from HBase client code
Date Thu, 10 Mar 2016 04:02:41 GMT

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

Enis Soztutar commented on HBASE-14963:
---------------------------------------

I just checked the patch again. It does not remove the dependency of guava from the client
module as the title suggests. It just changes an internal code path to not use guava, that
is all. 

I think this can go in all applicable branches. 

> Remove Guava dependency from HBase client code
> ----------------------------------------------
>
>                 Key: HBASE-14963
>                 URL: https://issues.apache.org/jira/browse/HBASE-14963
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>              Labels: needs_releasenote
>             Fix For: 2.0.0
>
>         Attachments: no-stopwatch.txt
>
>
> We ran into an issue where an application bundled its own Guava (and that happened to
be in the classpath first) and HBase's MetaTableLocator threw an exception due to the fact
that Stopwatch's constructor wasn't compatible... Might be better to not depend on Stopwatch
at all in MetaTableLocator since the functionality is easily doable without.



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

Mime
View raw message