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/08 23:49:20 UTC

[jira] [Comment Edited] (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=15558911#comment-15558911 ] 

Gopal Ramakrishnan edited comment on HBASE-14963 at 10/8/16 11:49 PM:
----------------------------------------------------------------------

Thanks [~busbey]. I did use the shaded client and got around the issue for the time being. I will join the other group to know more about the release.


was (Author: gopal_ramakrishnan@hotmail.com):
Thanks Sean Busbey. I did use the shaded client and got around the issue for the time being. I will join the other group to know more about the release.

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