What's New in Apache Phoenix

Cloudera Runtime 7.3.2:

IPv6 support for Phoenix

Starting with the 7.3.2 release, Phoenix client supports IPv6 with dual-stack functionality, allowing seamless communication over both IPv4 and IPv6 networks. This capability improves network scalability, future-proofs deployments, and enhances overall platform security.

For more information, see Enabling IPv6 support for Phoenix.

Phoenix supports cluster-wide metadata upgrade blocks

Phoenix now provides the ability to block cluster-wide metadata auto-upgrades. To prevent an upgrade from occurring, you must add a BLOCK_UPGRADE row in the SYSTEM.MUTEX or SYSTEM:MUTEX HBase table (depending on whether namespace mapping is enabled), in the 0:MUTEX_VALUE column family, before you start Phoenix with the upgraded versions. To add the row by using the HBase shell, run the following command:

put 'SYSTEM:MUTEX','BLOCK_UPGRADE','0:MUTEX_VALUE','MUTEX_LOCKED'

For a Java code example, see the LoadSystemTableSnapshotBase.java file in the Apache Phoenix repository.

Phoenix JDK 17 upgrade

Phoenix only supports JDK 17 starting with the 7.3.2 release; upgrading to JDK 17 ensures your application stays competitive and maintainable by providing improved performance, increased security, modern language features, and long-term support.

Deprecation of OMID service

The OMID service was deprecated in Cloudera Runtime 7.3.2 and will be removed in a future release. If you still require OMID, you can install the service through Cloudera Manager.

Apache Phoenix component upgraded to 5.2.1

The Phoenix runtime component upgrades from 5.1.3 to 5.2.1. This release delivers performance enhancements and introduces cluster-wide metadata upgrade blocks, providing you with greater control during upgrades and increasing stability in modern environments.