You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Rajeshbabu Chintaguntla (Jira)" <ji...@apache.org> on 2024/01/03 08:28:00 UTC
[jira] [Resolved] (OMID-254) Upgrade to phoenix-thirdparty 2.1.0
[ https://issues.apache.org/jira/browse/OMID-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajeshbabu Chintaguntla resolved OMID-254.
------------------------------------------
Fix Version/s: 1.1.1
Resolution: Fixed
Committed to master branch. Thanks for the patch [~nihaljain.cs] and review [~stoty].
> Upgrade to phoenix-thirdparty 2.1.0
> -----------------------------------
>
> Key: OMID-254
> URL: https://issues.apache.org/jira/browse/OMID-254
> Project: Phoenix Omid
> Issue Type: Sub-task
> Reporter: Nihal Jain
> Assignee: Nihal Jain
> Priority: Major
> Fix For: 1.1.1
>
>
> Phoenix-thirdparty has been released, see [https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
> {quote}The recent release has upgraded Guava to version 32.1.3-jre from the previous 31.0.1-android version. Initially, the 4.x branch maintained compatibility with Java 7, necessitating the use of the Android variant of Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move to the standard JRE version of Guava signifies a shift in compatibility standards
> {quote}
> It's time we bump up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)