HBase data model (column families) in Hadoop - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a column family in HBase?

A column family in HBase is a group of columns that are stored together physically. It helps organize data and improves read/write efficiency by grouping related columns.

beginner

How does HBase store data within column families?

HBase stores all columns of a column family together on disk. This means data in the same column family is stored in the same place, making access faster for those columns.

intermediate

Why should you keep the number of column families small in HBase?

Because each column family is stored separately, having many column families can slow down performance and increase storage overhead. It's best to keep column families few and group related columns.

beginner

Explain the relationship between rows, column families, and columns in HBase.

In HBase, data is organized as rows identified by a row key. Each row contains one or more column families. Each column family contains multiple columns. This hierarchy helps organize and access data efficiently.

intermediate

Can you add new columns to an existing column family in HBase without changing the schema?

Yes. HBase allows adding new columns dynamically within an existing column family without changing the table schema. This flexibility is a key feature of HBase's data model.

What does a column family in HBase group together?

A Indexes for faster search

B Rows with similar keys

C Tables with the same schema

D Related columns stored together physically

A column family groups related columns that are stored together physically to improve access speed.

Why is it recommended to keep the number of column families small in HBase?

A Because each column family requires separate storage and too many slow down performance

B Because column families cannot have more than 3 columns

C Because column families are deleted automatically if too many exist

D Because column families are only used for indexing

Each column family is stored separately, so many column families increase storage overhead and reduce performance.

In HBase, what is the smallest unit of data storage?

A Table

B Column family

C Cell (intersection of row and column)

D Region

A cell, which is the intersection of a row and a column, is the smallest unit of data storage in HBase.

Can you add new columns to an existing column family without changing the schema in HBase?

A Yes, columns can be added dynamically within a column family

B No, schema must be updated first

C Only if the table is recreated

D Only during off-peak hours

HBase allows adding new columns dynamically within existing column families without schema changes.

How are column families stored in HBase?

A All column families are stored together in one file

B Each column family is stored separately on disk

C Column families are stored in memory only

D Column families are stored as separate tables

Each column family is stored separately on disk to optimize access and storage.

Describe how data is organized in HBase using rows, column families, and columns.

Think about the hierarchy from row to column family to column.

Explain why it is important to limit the number of column families in an HBase table.

Consider how storage and performance relate to column families.

Practice

1. What is the main purpose of column families in HBase?

easy

A. To encrypt data automatically

B. To store data in rows instead of columns

C. To create indexes for faster searching

D. To group related columns together for better organization

Solution

1. Step 1: Understand the role of column families

   Column families group related columns in HBase tables to organize data logically.

2. Step 2: Identify the main purpose

   This grouping helps manage storage and access efficiently by keeping related data together.

3. Final Answer:

   To group related columns together for better organization -> Option D

4. Quick Check:

   Column families = Group related columns [OK]

Hint: Think of column families as folders grouping related files [OK]

Common Mistakes:

• Confusing column families with rows
• Thinking column families create indexes
• Assuming column families encrypt data

2. Which of the following is the correct way to define a column family in an HBase table schema?

easy

A. create 'mytable', 'cf1'

B. CREATE TABLE mytable (rowkey STRING, cf1:col1 STRING)

C. INSERT INTO mytable (cf1) VALUES ('value')

D. ALTER TABLE mytable ADD COLUMN cf1

Solution

1. Step 1: Recall HBase shell syntax for creating tables

   In HBase shell, tables are created with column families using: create 'table_name', 'column_family'

2. Step 2: Match the correct syntax

   create 'mytable', 'cf1' matches this syntax exactly, defining 'cf1' as a column family.

3. Final Answer:

   create 'mytable', 'cf1' -> Option A

4. Quick Check:

   HBase create table syntax = create 'table', 'cf' [OK]

Hint: Use HBase shell syntax: create 'table', 'column_family' [OK]

Common Mistakes:

• Using SQL syntax instead of HBase shell
• Trying to add columns like in relational DBs
• Confusing insert with create commands

3. Given an HBase table with column families cf1 and cf2, what happens if you insert data only into cf1:colA for a row?

medium

A. Only cf1:colA stores data; cf2 columns remain empty for that row

B. Data is automatically copied to cf2

C. The row is rejected because all column families must have data

D. The entire row is deleted

Solution

1. Step 1: Understand column family independence

   In HBase, column families are independent; data can be stored in any family without affecting others.

2. Step 2: Analyze the effect of inserting data into one family

   Inserting data into cf1:colA stores data only there; cf2 columns remain empty for that row.

3. Final Answer:

   Only cf1:colA stores data; cf2 columns remain empty for that row -> Option A

4. Quick Check:

   Column families store data independently [OK]

Hint: Data in one column family doesn't affect others [OK]

Common Mistakes:

• Assuming data copies across column families
• Thinking all families must have data per row
• Believing row is deleted if some families are empty

4. You tried to create an HBase table with this command: create 'mytable' 'cf1' 'cf2' but got an error. What is the likely cause?

medium

A. You cannot create multiple column families in one command

B. The syntax requires column families as separate arguments with commas

C. Column family names must be enclosed in double quotes

D. Table names cannot contain numbers

Solution

1. Step 1: Review HBase create table syntax

   The correct syntax is: create 'table_name', 'cf1', 'cf2' with commas between column families.

2. Step 2: Identify the error in the command

   The command is missing commas between column families, which is invalid syntax in HBase shell.

3. Final Answer:

   The syntax requires column families as separate arguments with commas -> Option B

4. Quick Check:

   HBase create syntax = with commas between column families [OK]

Hint: List column families with commas in create command [OK]

Common Mistakes:

• Omitting commas between column families
• Using quotes incorrectly
• Thinking table names can't have numbers

5. You want to design an HBase table to store customer data with addresses and orders. Which is the best way to use column families?

hard

A. Create one column family for all data: 'cf_all'

B. Create a column family per customer

C. Create separate column families like 'address' and 'orders' to group related columns

D. Store addresses as rows and orders as columns in one family

Solution

1. Step 1: Understand column family design principles

   Column families group related columns to improve performance and reflect real-world categories.

2. Step 2: Apply to customer data scenario

   Separating 'address' and 'orders' into different column families groups related data logically and optimizes storage.

3. Final Answer:

   Create separate column families like 'address' and 'orders' to group related columns -> Option C

4. Quick Check:

   Use column families to group related data categories [OK]

Hint: Group related data in separate column families for clarity [OK]

Common Mistakes:

• Putting all data in one family causing inefficiency
• Creating a family per customer wastes resources
• Mixing rows and columns incorrectly