Geek Answers Handbook

Apache Phoenix vs Hbase Native API

I use Apache Phoenix to simplify searching and updating data in Hbase. But I would like to know, in terms of performance , what would be better? Phoenix or Custom wrapper using the Hbase Native API? Or do we have any other approach that does not affect performance?

+4
source share
2 answers

In an ideal world, Native api will work faster, but you will need to work on it all the time, because develop a good api for Hbase is a separate project. Great project.

And you will need a great understanding of the internal process of map-reduce and hbase. But Phoenix already does all this for you. For example, Secondary indexing to create and automatically maintain global indexes over your main table. Queries automatically use the index when it is more efficient, turning your complete tables into scans by points and ranges. Multiple columns can be indexed in ascending or descending order. Additional columns of the primary table may be included in the index to form a closed index. Available in two flavors: Server-side index maintenance for mutable data. Client-side index maintenance is optimized for one-time, application-only applications.

, Phoenix skip-scan . ... http://phoenix-hbase.blogspot.com/ http://phoenix.apache.org/performance.html#

, , , api. , .

Hive SparkSQL. Hive , Spark - , .

SparkOnHbase http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ , . , Hbase native. .

+3

Phoenix , SQL- HBase, Hbase. , , , API Hbase, . , Hbase-. salesforce, . , .

0

More articles:


All Articles