Answer:

There are 3 different types of tombstone markers in HBase for deletion-

• Family Delete Marker- This marker marks all columns for a column family.
• Version Delete Marker-This marker marks a single version of a column.
• Column Delete Marker-This markers mark all the versions of a column.

Answer: HBase should be used when the big data application has –

• A variable schema
• When data is stored in the form of collections
• If the application demands key-based access to data while retrieving.

Key components of HBase are –

• Region- This component contains memory data store and Hfile.
• Region Server-This monitors the Region.
• HBase Master-It is responsible for monitoring the region server.
• Zookeeper- It takes care of the coordination between the HBase Master component and the client.
• Catalog Tables-The two important catalog tables are ROOT and META.ROOT table tracks where the META table is and META table stores all the regions in the system.

Answer:

HBase and Hive both are completely different Hadoop based technologies-Hive is a data warehouse infrastructure on top of Hadoop whereas HBase is a NoSQL key-value store that runs on top of Hadoop. Hive helps SQL savvy people to run MapReduce jobs whereas HBase supports 4 primary operations-put, get, scan and delete. HBase is ideal for real-time querying of big data where Hive is an ideal choice for analytical querying of data collected over the period of time.

Answer:

Every row in an HBase table has a unique identifier known as RowKey. It is used for grouping cells logically and it ensures that all cells that have the same RowKeys are co-located on the same server. RowKey is internally regarded as a byte array.

Answer:

RDBMS is a schema-based database whereas HBase is schema-less data model.

• RDBMS does not have support for in-built partitioning whereas in HBase there is automated partitioning.
• RDBMS stores normalized data whereas HBase stores de-normalized data.

Answer:

Record Level Operational Commands in HBase are –put, get, increment, scan and delete.

Table Level Operational Commands in HBase are-describe, list, drop, disable and scan.

Answer:

The two important catalog tables in HBase, are ROOT and META. ROOT table tracks where the META table is and META table stores all the regions in the system.

Answer:

On issuing a delete command in HBase through the HBase client, data is not actually deleted from the cells but rather the cells are made invisible by setting a tombstone marker. The deleted cells are removed at regular intervals during compaction.

Answer:

The logical deviation of data is represented by a key known as column Family. Column families consist of the basic unit of physical storage on which compression features can be applied. In an already populated database, when the block size of column family is altered, the old data will remain within the old block size whereas the new data that comes in will take the new block size. When compaction takes place, the old data will take the new block size so that the existing data is read correctly.

Answer:

All edits in the HStore are stored in the HLog. Every region server has one HLog. HLog contains entries for edits of all regions performed by a particular Region Server.WAL abbreviates to Write Ahead Log (WAL) in which all the HLog edits are written immediately.WAL edits remain in the memory till the flush period in case of deferred log flush.

Answer:

Apache HBase is a type of “NoSQL” database. “NoSQL” is a general term meaning that the database isn’t an RDBMS which supports SQL as its primary access language, but there are many types of NoSQL databases: BerkeleyDB is an example of a local NoSQL database, whereas HBase is very much a distributed database. Technically speaking, HBase is really more a “Data Store” than “Data Base” because it lacks many of the features you find in an RDBMS, such as typed columns, secondary indexes, triggers, and advanced query languages, etc.

Answer: It is a file which lists the known region server names.

Answer: The key components of HBase are Zookeeper, RegionServer, Region, Catalog Tables and HBase Master.

Answer: Hbase is used because it provides random read and write operations and it can perform a number of operation per second on a large data sets.

Answer: It is a default mode of HBase .In standalone mode, HBase does not use HDFS—it uses the local filesystem instead—and it runs all HBase daemons and a local ZooKeeper in the same JVM process.

Answer: HBase supports those OS which supports java like windows, Linux.

Answer: Apache HBase has many features which support both linear and modular scaling, HBase tables are distributed on the cluster via regions, and regions are automatically split and re-distributed as your data grows(Automatic sharding).HBase supports a Block Cache and Bloom Filters for high volume query optimization(Block Cache and Bloom Filters).

Answer: HDFS doesn’t provide fast lookup records in a file, IN Hbase provides fast lookup records for a large table.