phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4262) Create shaded packages to shade all uses of Guava
Date Sun, 01 Oct 2017 20:08:00 GMT

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

Josh Elser commented on PHOENIX-4262:
-------------------------------------

IMO, the solution when working across disjoint software projects like this is to shade/relocate
all of the dependencies that we use.

While, in the common case, it bloats the size of a Phoenix installation (given Hadoop and
HBase would both provide their own), it prevents us from having to be proactive in catching
any upgrades to Guava that the HBase community enacts that would otherwise break Phoenix.

> 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