[
https://issues.apache.org/jira/browse/PHOENIX-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804602#comment-17804602
]
ASF GitHub Bot commented on PHOENIX-7158:
-----------------------------------------
NihalJain commented on PR #125:
URL:
https://github.com/apache/phoenix-connectors/pull/125#issuecomment-1882525200
> @NihalJain The broken Jenkins CI is known issue, see
https://issues.apache.org/jira/browse/PHOENIX-7129 . The current workaround is
ignoring the Apache CI results, and relying on the github actions check result.
Thank you for your response @stoty. Will look at github actions results,
going ahead.
> I have replied to the log4j issue on its ticket.
Also, let me try to see if I can fix log4j issue.
> Update Connectors to phoenix-thirdparty 2.1.0
> ---------------------------------------------
>
> Key: PHOENIX-7158
> URL: https://issues.apache.org/jira/browse/PHOENIX-7158
> Project: Phoenix
> Issue Type: Improvement
> Components: connectors
> Reporter: Nihal Jain
> Assignee: Nihal Jain
> Priority: Major
>
> 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. Also, now PHOENIX-7116 is in place so we can pull this
> to branch 5.1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
