Figure out future for Phoenix connector

[mosabua]

The connector continues to be hard to maintain. Specifically with the upgrade to Java 24 by March 2025 this is going to be tricky again. See #23498

We will ask for community feedback about potential removal in the Trino Summit keynote and the following maintainer and contributor calls.

Potentially a hbase connector could also help but there is nothing happening on that front either and it might have similar technical challenges as well.

At this stage we might end up removing the connector unless we find contributors helping with it.

We will reach out to the Phoenix community again as well.

[mosabua]

fyi @wendigo @monimiller

[soenkeliebau]

also fyi @stoty

[stoty]

What is the specific problem with Phoenix and JDK24 ?

Is it SecurityManager and Subject.getSubject() related changes ?

There is a refection based worakround for those in Jetty that we can copy, but since most of that code is coming from Hadoop, it needs to be fixed there.

Depending on the release schedules, March may not be a realistic deadline for that.

[hashhar]

CVEs is the main problem.
A secondary problem is use and presence of code which uses statics (Hadoop libraries) which causes issues with dynamic catalogs feature (cannot unload / load stuff like that safely without risk of leaking things).

[stoty]

Are you using phoenix 5.2.1 ?

Phoenix 5.2.1 and the upcoming HBase 2.6.2 will work with the latest Hadoop 3.4.1 release.

There is a fair chance for HBase 2.6.2 to be released by next March.

[wendigo]

@stoty yes we are using 5.2.1

[monimiller]

this will impact multiple starburst users currently utilizing the connector