You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2020/07/15 04:32:00 UTC

[jira] [Created] (PHOENIX-6010) Create phoenix-thirdparty, and consume guava through it

Istvan Toth created PHOENIX-6010:
------------------------------------

             Summary: Create phoenix-thirdparty, and consume guava through it
                 Key: PHOENIX-6010
                 URL: https://issues.apache.org/jira/browse/PHOENIX-6010
             Project: Phoenix
          Issue Type: Improvement
          Components: core, omid, tephra
    Affects Versions: 5.1.0, 4.16.0
            Reporter: Istvan Toth
            Assignee: Istvan Toth


We have long-standing and well-documented problems with Guava, just like the rest of the Hadoop components.

Adopt the solution used by HBase:
 * create phoenix-thirdparty repo
 * create a pre-shaded phoenix-shaded-guava artifact in it
 * Use the pre-shaded Guava in every phoenix component

The advantages are well-known, but to name a few:
 * Phoenix will work with Hadoop 3.1.3+
 * One less CVE in our direct dependencies
 * No more conflict with our consumer's Guava versions



--
This message was sent by Atlassian Jira
(v8.3.4#803005)