hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14963) Remove use of Guava Stopwatch from HBase client code
Date Sat, 08 Oct 2016 04:55:20 GMT

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

Sean Busbey commented on HBASE-14963:

[~gopal_ramakrishnan@hotmail.com] the 1.3 release line has not yet started producing releases.
To get information on how that release line is progressing, I'd recommend searching / joining
the dev@hbase mailing list.

In the meantime, you can use the hbase-shaded-client in releases 1.1+.

> 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

View raw message