What's New in Apache Phoenix
Learn about the new features of Phoenix in Cloudera Runtime 7.2.9.
Apache Phoenix 5.1.0
Apache Phoenix version in Cloudera Runtime 7.1.9 is Apache Phoenix 5.1.0. You can read about the new capabilities in this page. For more information about all the fixes and improvements in Apache Phoenix 5.1.0, see the Release 5.1.0 section in the Phoenix changelog.
X-row, X-table transaction support enables support for complex distributed transactions. Transaction support enables you to run atomic database operations, meaning your database operations must either be completed or terminated.
This two-phase commit capability is implemented using ANSI SQL semantics which is the same as used in other databases like MySQL or PostgreSQL, but this implementation benefits from the near-linear scalability of Apache HBase and Apache Phoenix, and do not have upper-bound on the number of transactions, size of rows/table, or size per table like other databases.
For more information about transaction support, see Transaction Support.
For more information about benchmark results, see the Bringing Transaction Support to Cloudera Operational Database blog post.
Strongly consistent indexing support
Strongly consistent indexing is a three-phase indexing algorithm that ensures that the index table is always in sync with the data table. Newly created Apache Phoenix tables use strongly consistent indexing by default. You can migrate your old Apache Phoenix tables to use strongly consistent indexing.
For more information about strongly consistent indexing, see Strongly consistent indexing.
Support for Apache Phoenix in Hue
Apache Phoenix dialect is available out of the box in Hue when the cluster is created using the “Operational Database with SQL” cluster template.
For more information, see Using SQL to query HBase from Hue.