From my understanding, Hbase is the Hadoop database and Hive is the data warehouse.
Hive allows to create tables and store data in it, you can also map your existing HBase tables to Hive and operate on them.
why we should use hbase if hive do all that? can we use hive by itself? I'm confused :(
So in simple terms, with hive you can fire SQL like queries (with some exceptions) on your table/s and is used in batch operation. While with hbase, you can do real time querying and is based on key value pair.
"why we should use hbase if hive do all that? can we use hive by itself" Because Hive doesn't supports updating your data set. So if you have large analytical processing application use Hive and if you have real time get/set/update request processing, use Hbase.
| Sr. No. | Key | Hive | HBase |
|---|---|---|---|
| 1 | Definition | Apache Hive is an open source data warehouse system built on top of Hadoop used for querying and analyzing large data in form of structured and semi-structured stored in Hadoop files. | On other hand HBase is a non-relational column-oriented distributed database which runs on the top of HDFS. Moreover it is a NoSQL open source database that stores data in rows and columns. |
| 2 | Processing | Hive is mainly used for batch processing and thus is known as OLAP. Also Real time processing is not possible in case of Hive. | On other hand HBase is mainly used for transactional processing and known as OLTP. However Real time processing is possible in case of HBase. |
| 3 | Query type | Hive is used only for analytical queries. | On other hand HBase is used for real time query instead of Analytical query as in case of Hive. |
| 4 | Type | Hive is not a dataBase and has schema model. | On other hand HBase is a type of NoSQL database and is free from schema model. |
| 5 | Latency | High latency operations are supported in case of Hive. | On other hand in case of HBase only low level latency operations are allowed or supported. |
