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 18:59:00 GMT

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

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

bq. We would need to provide a separate artifact with our dependencies, modify our code to
use shaded packages and after that deal with the difference server/client because we do not
shade anything on server side because it uses the dependencies that HBase provides

Yes. I think something like this should be done for the client. Fact of life when working
with Guava. Take complaint to the Guava maintainers. Perhaps it is possible to use a Maven
target to shade Guava into the client fat jar and rewrite the bytecode of the referring Phoenix
classes to avoid having to make any source level changes.



> 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