You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2021/09/17 21:20:00 UTC

[jira] [Reopened] (PHOENIX-6234) Replace Guava with phoenix-thirdparty version in 4.x

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

Geoffrey Jacoby reopened PHOENIX-6234:
--------------------------------------
      Assignee: Geoffrey Jacoby

Alas, it looks like [~jainankit] and I are going to need this for a phoenix-connector feature we're looking to add to Phoenix 4.17 / 5.2, that has a dependency that requires a modern guava. Shading guava will likely be less disruptive on downstream projects than increasing 4.17's unshaded dependency and letting our users deal with the fallout. 

Reopening and assigning to myself. 

> Replace Guava with phoenix-thirdparty version in 4.x
> ----------------------------------------------------
>
>                 Key: PHOENIX-6234
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6234
>             Project: Phoenix
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 4.16.0
>            Reporter: Istvan Toth
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>
> As discussed on the dev list, applying the Guava changes from PHOENIX-6010 on the 4.x branch would make our lives easier.
> 99% percent of the change is search-and-replace, the remaining 1% can probably be lifted from the master commit.



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