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 Sat, 12 Dec 2015 00:57:46 GMT

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

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

Yes, we have a shaded client already, but it is pretty new. Not everybody (for example in
this context Phoenix + Storm JDBC) is still using the non-shaded client. I'm +1 to do this
as a convenience fix for existing clients. 

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