Behavioral Changes in Phoenix

Functional adjustments and behavioral updates for Phoenix are introduced in Cloudera Runtime 7.3.2, its service packs, and cumulative hotfixes.

Cloudera Runtime 7.3.2.10000 SP1

Summary: Phoenix is updated to comply with FIPS 140-3 cryptographic requirements

Previous behavior:

Phoenix used cryptographic algorithms that are not approved under FIPS 140-2 or FIPS 140-3. In FIPS-enabled cluster deployments, this caused the Phoenix Query Server to fail to start, JDBC connection failures due to non-FIPS-approved TLS cipher suites, and query execution errors.

New behavior:

Phoenix is updated to replace all non-FIPS-compliant cryptographic operations with FIPS-approved equivalents. Following are the key changes:

Phoenix JDBC connections now accept only FIPS 140-3-approved TLS cipher suites. You must configure Phoenix clients to use FIPS-compliant cipher suites before connecting to a FIPS-enabled cluster.
For clusters upgraded to Cloudera Runtime 7.3.2.10000 with FIPS mode enabled, you must re-encrypt any existing Phoenix system table credentials using the updated key derivation scheme before running Phoenix queries.

Cloudera Runtime 7.3.2.100 CHF 1

There are no behavioral changes in this release.

Cloudera Runtime 7.3.2

There are no behavioral changes in this release.