Apache Phoenix Benefits and Insights

Why use Apache Phoenix?

Key differentiators & advantages of Apache Phoenix

Accessible: Interacts easily with HBase SQL, enabling accessibility for those with limited knowledge of HBase API. Translates SQL into native HBase API calls with driver APIs.
Faster Processing: Custom filters and coprocessors help perform functions on the server-side. It minimizes data transfer from both the client-side and server-side.
Real-Time Data Streaming: HBase as a data storage solution helps accelerate data query quickly and efficiently on a large scale.
SQL Interface: Breaks the NoSQL barrier by providing an SQL interface for Hbase through the JDBC driver.
Integration: Supports MapReduce integration through its ability to customize both input and output formats. By integrating the spark plugin, it leverages any underlying splits to store and recover data across multiple workers.
Performance Optimization: Optimizes performance by reducing disk storage and offering indirection between column qualifier and column name. Also helps pack every value into a single cell of the same column. Enhance time-series data by identifying which files to scan and which to skip, according to the minimum time range set.

Industry Expertise

Businesses in multiple industries worldwide rely on its ability to load and run interactive queries. The top sectors include computer software, business services, finance, manufacturing, telecommunications, retail, healthcare and more.

Key Features

User-Defined Functions (UDFs): Create and deploy temporary, permanent or domain-specific scalar functions to the cluster. The same UDFs can act as built-in functions - upsert, delete and insert.
Data Access: Secondary indexing helps access data from its primary pathway. It develops an alternate row key that allows point lookups to find their way through a new axis. Create indexes over both mutable and immutable data.
- Covered Indexes: Includes primary, secondary and any data table key columns to cover queries.
- Functional Indexes: Create indexes on columns and arbitrary expressions.
  - Local Indexing: Supports indexing for use cases that are space-constrained and write-heavy. Also allows indexing if the query is not fully covered.
  - Global Indexing: Supports indexing for read-heavy use cases to select the index table to use that will produce the fastest query time.
Schema Mapping: Create a schema mapped to the namespace of HBase instead of assigning a default namespace to every table.
Bulk Loader: Supports bulk loading of CSV files into HBase using a client-side script or MapReduce.
Multi-Tenancy: Different tenants can create independent views of the same physical HBase table. Possible only on a per-connection basis.
Table Sample: Restricts the returning of rows from a table, similarly to T-SQL syntax and PostgreSQL.

Limitations

At the time of this review, these are the limitations according to user feedback:

Limited support for CROSS JOIN and FULL OUTER JOIN.
Client-side batching lacks proper transaction support.
Can’t access data from different sources; only data stored in HBase is accessible.

Suite Support

Before creating a support ticket, it is best to discuss the issues on the public mailing list. The vendor has separate mailing lists - user, developer, private and commits for different queries. Each of these mailing lists has a subscribe, an unsubscribe and a post link. Subscribe to the required link source for issue resolution.

Email: Not specified.

Phone: Not specified.

Training: Not available from the vendor. Instead, enroll in courses to receive training from a certified credentialing body.

Tickets: Submit a support ticket after logging in to the vendor’s portal.

Apache Phoenix Reviews & Pricing

What is Apache Phoenix?

#61