[
https://issues.apache.org/jira/browse/PHOENIX-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817656#comment-17817656
]
ASF GitHub Bot commented on PHOENIX-7193:
-----------------------------------------
wendigo commented on PR #1810:
URL: https://github.com/apache/phoenix/pull/1810#issuecomment-1945998086
@stoty sorry for unrelated question, but is the new release happening
anytime soon?
In trinodb/trino we are considering dropping Phoenix 5 support because of
the high number of critical CVEs included in the shaded client jar.
> Fix cluster override for mapreduce jobs for non-ZK registries
> -------------------------------------------------------------
>
> Key: PHOENIX-7193
> URL: https://issues.apache.org/jira/browse/PHOENIX-7193
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.2.0, 5.1.4
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> The Mapreduce cluster override code is heavily hardwired to ZK cluster
> definitions.
> When I added the non-ZK registry support, I just hacked the tests so that
> they run, but I did not add the possibility of overriding the clusters for
> non-ZK registries.
> This came back to bite me during the HBase 3 work.
> This patch adds new MR parameters to override the Phoenix JDBC input/output
> URLs, and cleans up some of the accumulated mess.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
