What's New in Apache Phoenix
Learn about the new features of Phoenix in Cloudera Runtime 7.3.1.0.
Phoenix now supports alternate HBase connection registries
You can now use the Phoenix thick client using additional HBase connection registries. Phoenix now supports a Zookeeper-less connection strategy using a Master Registry implementation.
Phoenix now introduces the following JDBC URL variants.
jdbc:phoenix+zk: Uses Zookeeper. This is the original registry supported since the inception of HBase and Phoenix.jdbc:phoenix+rpc: Uses RPC to connect to the specified HBase Region Server or Master nodes.jdbc:phoenix+master: Uses RPC to connect to the specified HBase Master nodes.
For more information, see .
Phoenix FIPS support
Phoenix is now Federal Information Processing Standards (FIPS) compliant. For more information, see Phoenix is FIPS compliant.
Phoenix supports rolling restart
If Phoenix service instances are running on multiple nodes, while performing a rolling restart the Phoenix services are restarted one after another ensuring zero downtime.
The OMID service also supports rolling restart and the High Availability (HA) mode for the OMID TSO server. If OMID service instances are running on multiple nodes, while performing a rolling restart the OMID services are restarted one after another ensuring zero downtime. For more information, see Preparing for a Zero Downtime Upgrade.
Phoenix supports JDK 17
Phoenix supports Oracle JDK version 17.0.6 starting from CDP Runtime 7.1.9. For more information on JDK 17, see Java Requirements.
Operating system support
Phoenix is now supported on the following operating systems:
- RHEL-9.1
- RHEL-8.8
- RHEL-8.8 FIPS
- Oracle-8.8 UEK
- SLES-15 SP4 for x86
