Integrating Hive and HBase at Facebook ☞
Keywords: hive,hadoop,hbase,cassandra,facebook,NoSQL, NoSQL databases, NoSQL community, the definitive guide to NoSQL
While definitely interesting, something doesn’t seem to add up:
It (nb HBase) sidesteps Hadoop’s append-only constraint by keeping recently updated data in memory and incrementally rewriting data to new files, splitting and merging intelligently based on data distribution changes. Since it is based on Hadoop, making HBase interoperate with Hive is straightforward, meaning HBase tables can be accessed as if they were native Hive tables. As a result, a single Hive query can now perform complex operations such as join, union, and aggregation across combinations of HBase and native Hive tables. Likewise, Hive’s INSERT statement can be used to move data between HBase and native Hive tables, or to reorganize data within HBase itself.
What I seem to not understand is:
- Facebook is already using Cassandra
- Cassandra works well with Hadoop, at least starting with version 0.6.0
- Hive works on top of Hadoop
So why HBase?
