You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/06/22 03:15:00 UTC

[jira] [Assigned] (HBASE-17908) Upgrade guava

     [ https://issues.apache.org/jira/browse/HBASE-17908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack reassigned HBASE-17908:
-----------------------------

        Assignee: stack
    Hadoop Flags: Incompatible change
    Release Note: 
Move to a relocated guava 22.0.

Incompatible change. ReplicationEndpoint and subclasses extends guava Service which changed pretty radically between 12.0 and 22.0. Change is kosher because implementations are marked audience private. Still, this will likely cause grief for the likes of the downstream lily indexer.

> Upgrade guava
> -------------
>
>                 Key: HBASE-17908
>                 URL: https://issues.apache.org/jira/browse/HBASE-17908
>             Project: HBase
>          Issue Type: Sub-task
>          Components: dependencies
>            Reporter: Balazs Meszaros
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> Currently we are using guava 12.0.1, but the latest version is 21.0. Upgrading guava is always a hassle because it is not always backward compatible with itself.
> Currently I think there are to approaches:
> 1. Upgrade guava to the newest version (21.0) and shade it.
> 2. Upgrade guava to a version which does not break or builds (15.0).
> If we can update it, some dependencies should be removed: commons-collections, commons-codec, ...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)