Apache Phoenix Reviews & Product Details

SQL like syntax is the only thing positive Review collected by and hosted on G2.com.

Apache Phoenix is still very primitive and does not offer easy SQL syntaxes. The errors/ exceptions are hard to understand, and development is slow. Review collected by and hosted on G2.com.

Apache Phoenix provides access to data that's stored in HBase which is a column oriented database. HBase doesn't natively support SQL or really any query language. The HBase shell has a scan command for accessing data but I find it extremely awkward to use. Phoenix "puts the SQL back in NoSQL" so that means if you know SQL you can query data in HBase using a language you know.

While there are multiple ways to access data in HBase through SQL including Apache Hive, Impala and Drill, I think Apache Phoenix has a better design than any of the alternatives. Unlike most relational databases that require schema design before you can add data, HBase is essentially schemaless. However all of these tools require a schema, so that means in order to use them you have to fist map the fields in HBase (at least the ones you want to use) to a metadata layer. Hive/Impala, Drill and Phoenix each do this in their own unique way, but I think the way you do this in Phoenix is the most logical.

Also in my experience Phoenix provides better throughput than any of the alternatives because it converts SQL queries into HBase scans. Review collected by and hosted on G2.com.

You do have to create the Phoenix schema manually.

Unlike the alternatives Phoenix can only access data stored in HBase, so if you want to combine data from different data sources, such as CSV or JSON files you need to use something else. Review collected by and hosted on G2.com.

Complete and flexible ACID transaction capacity, NoSQL schema reading by taking advantage of speed and fast HBase query. Review collected by and hosted on G2.com.

Everything has to be done manually, an error is difficult to find to correct with the lack of data and information. Review collected by and hosted on G2.com.

Through documentation is available which makes it easy to start and setup.

One gets to work with the comfortable SQL syntax without being bothered to crawl through HBase help docs for shell syntax. Review collected by and hosted on G2.com.

Tables created from HBase shell have to be mapped separately in Phoenix.

Bulk loading data to tables created via Phoenix is not as straight forward as for tables created from HBase shell.

Apache Phoenix's capabilities depends heavily on HBase coprocessors making it tightly coupled to HBase Architecture, which is a challenge as Phoenix needs to be revamped with every Major release of Apache HBase, and due to this fact Apache Phoenix is less reliant in Production environment.

Switching through Index (Global to Local and vice versa)on a table becomes a pain point.

Integration with Apache Spark needs to be improved on. Review collected by and hosted on G2.com.

When working with high volume of data, Apache phoenix will provide high performance and helps you in performance tuning and also provide some additional features which will help you get the results faster in very less time for complex query also. Review collected by and hosted on G2.com.

It is new and open source so you have to explore most of the things by yourself. The more you explore the more you like this. Review collected by and hosted on G2.com.

Response time ~ hbase query, SQL support with JDBC standards

Phoenix is developing gradually and with hbase 2.0 support it has reached good.

It's the option explored when we wanted something cheap which can sit inside our emr cluster.

having EMR is good on it. Review collected by and hosted on G2.com.

installation steps, no window func, not using proper error message instead giving stacktrace (though sometimes more useful) but should be logged, spark support was very late, documentation is not verbose, bad orm library (not widely supported by other ORM))

unfortunately phoenix popularity is dependent on hbase, and hbase is somewhat not in talks very much.

I find no cloud provider is giving serverless hbase/phoenix hosting.

EMR is managed but emr support team is quite limited with knowledge with in phoenix specially. Review collected by and hosted on G2.com.

Integrate Apache HBase and automatic database backup Review collected by and hosted on G2.com.

I have no problems with integration and extra API Review collected by and hosted on G2.com.

It helped me a lot in dealing with Hbase data. As i can't directly execute sql query on HBase, it enabled me to execute sql like query to deal with data.

Also the support was easily available on internet if i get stuck somewhere.

Configuring it with the application and setting it up was also very easy.

It made the work with large amount of data very easy without any performance issue. Review collected by and hosted on G2.com.

At one side it's strong point is that enables query execution and on the other side it's limitation is also with query. As it doesn't support update command in starting i faced a lot of issue.

Upsert command is there but still in many scenarios i faced much difficulty to properly execute it.

If we can have update command in this it would be a very good point so this can be improved. Review collected by and hosted on G2.com.

We use hortonworks with hbase as our back end system. we have Apache phoenix on top of it , which is used by our BI team. Review collected by and hosted on G2.com.

Using ETL tools for more transformations, its not that easy as typical MSSQL Servers Review collected by and hosted on G2.com.

We can use SQl operations without knowing hbase query syntax. Review collected by and hosted on G2.com.

The Phoenix JDBC driver normalizes column names, but the Phoenix-Spark integration does not perform this operation while loading data from Phoenix Table. Review collected by and hosted on G2.com.