You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gopal Ramakrishnan (JIRA)" <ji...@apache.org> on 2016/10/07 23:00:25 UTC

[jira] [Commented] (HBASE-14963) Remove use of Guava Stopwatch from HBase client code

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

Gopal Ramakrishnan commented on HBASE-14963:
--------------------------------------------

I am running in to the same issue and i see that it is fixed as part of this issue. How will i be able to get this fix? I am not able to find the 1.4 or 2.0 version of the hbase client on the maven repository. https://mvnrepository.com/artifact/org.apache.hbase/hbase-client


> Remove use of Guava Stopwatch 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, 1.3.0, 1.4.0
>
>         Attachments: HBASE-14963-branch-1.patch, 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)