HBase data model (column families) in Hadoop - Step-by-Step Execution

Concept Flow - HBase data model (column families)

Start: Create Table

↓

Define Column Families

↓

Store Data in Column Families

↓

Retrieve Data by Column Family

↓

End

This flow shows how an HBase table is created with column families, data is stored inside them, and then retrieved by column family.

Execution Sample

Hadoop

create 'mytable', 'info', 'stats'
put 'mytable', 'row1', 'info:name', 'Alice'
put 'mytable', 'row1', 'stats:visits', '5'
get 'mytable', 'row1', {COLUMN => 'info:name'}

Create a table with two column families, add data to each family, then get data from one family.

Execution Table

Step	Command	Action	Result
1	create 'mytable', 'info', 'stats'	Create table 'mytable' with column families 'info' and 'stats'	Table 'mytable' created with 2 column families
2	put 'mytable', 'row1', 'info:name', 'Alice'	Store 'Alice' in 'info:name' for row 'row1'	Data stored in 'info' family under 'name' qualifier
3	put 'mytable', 'row1', 'stats:visits', '5'	Store '5' in 'stats:visits' for row 'row1'	Data stored in 'stats' family under 'visits' qualifier
4	get 'mytable', 'row1', {COLUMN => 'info:name'}	Retrieve 'info:name' from 'row1'	Returns 'Alice' from 'info' family

💡 All commands executed; data stored and retrieved by column family.

Variable Tracker

Variable	After Step 1	After Step 2	After Step 3	After Step 4
Table 'mytable'	Created with column families 'info', 'stats'	Row 'row1' has 'info:name'='Alice'	Row 'row1' has 'stats:visits'='5'	No change; data retrieved from 'info:name'

Key Moments - 2 Insights

Why do we define column families before adding data?

Column families group related columns and define storage settings. You must create them first (see Step 1) before storing data in those families (Steps 2 and 3).

Can data from one column family be retrieved without accessing others?

Yes, as shown in Step 4, you can get data from a specific column family without reading other families, improving efficiency.

Visual Quiz - 3 Questions

Look at the execution table, what column family stores the 'visits' data?

A info

B stats

C name

D row1

💡 Hint

Check Step 3 in the execution table where 'stats:visits' is stored.

At which step is the table 'mytable' created with column families?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at Step 1 in the execution table for table creation.

If you want to retrieve 'Alice' from 'info:name', which command is used?

A put 'mytable', 'row1', 'info:name', 'Alice'

B get 'mytable', 'row1', {COLUMN => 'info:name'}

C create 'mytable', 'info', 'stats'

D put 'mytable', 'row1', 'stats:visits', '5'

💡 Hint

Check Step 4 in the execution table for data retrieval.

Concept Snapshot

HBase tables have column families grouping columns.
Define column families when creating the table.
Store data by specifying 'family:qualifier'.
Retrieve data by column family for efficiency.
Column families control storage and access patterns.

Full Transcript

This visual execution shows how to create an HBase table with column families, store data in them, and retrieve data by specifying the column family. First, the table 'mytable' is created with two column families: 'info' and 'stats'. Then, data 'Alice' is stored in the 'info' family under the 'name' qualifier for row 'row1'. Next, the number '5' is stored in the 'stats' family under the 'visits' qualifier for the same row. Finally, data is retrieved from the 'info:name' column, returning 'Alice'. This demonstrates how column families organize data and allow efficient access.

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