[
https://issues.apache.org/jira/browse/HBASE-10174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849661#comment-13849661
]
Lars Hofhansl commented on HBASE-10174:
---------------------------------------
It's certainly better to make HBase work with the various versions of Guava out
there.
I'm still confused, though. This would be an issue if the *client* used the
Guava classes, right? Surely nobody would need to upgrade Guava on the HBase
server (unless one has custom filters or coprocessors that use a newer Guava,
in which case I'd say "tough luck").
If we use Guava on the client, I'd agree that we not force a client application
to a specific version of Guava just due to the way we're using it. The changed
classes are server only?
> Back port HBASE-9667 'NullOutputStream removed from Guava 15' to 0.94
> ---------------------------------------------------------------------
>
> Key: HBASE-10174
> URL: https://issues.apache.org/jira/browse/HBASE-10174
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 0.94.15
>
> Attachments: 10174-v2.txt, 9667-0.94.patch
>
>
> On user mailing list under the thread 'Guava 15', Kristoffer Sjögren reported
> NoClassDefFoundError when he used Guava 15.
> The issue has been fixed in 0.96 + by HBASE-9667
> This JIRA ports the fix to 0.94 branch
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
