phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4262) Create shaded packages to shade all uses of Guava
Date Mon, 02 Oct 2017 16:25:00 GMT

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

Andrew Purtell commented on PHOENIX-4262:
-----------------------------------------

bq. it prevents us from having to be proactive in catching any upgrades to Guava that the
HBase community enacts that would otherwise break Phoenix.

Any incompatibilities with Guava on the classpath in the client environment too, which is
a bigger problem IMHO

> Create shaded packages to shade all uses of Guava
> -------------------------------------------------
>
>                 Key: PHOENIX-4262
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4262
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Chinmay Kulkarni
>
> The Phoenix build breaks if we upgrade the Guava version to say, 20.0 due to lack of
backward compatibility. 
> To handle this, we can perhaps use shaded packages to avoid dependency conflicts at runtime.



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

Mime
View raw message