HGETALL for all fields in Redis - Time & Space Complexity

Time Complexity: HGETALL for all fields

O(n)

Understanding Time Complexity

When we ask how long a Redis command takes, we want to know how its work grows as the data grows.

For HGETALL, we want to see how the time changes when the number of fields in a hash changes.

Scenario Under Consideration

Analyze the time complexity of the following Redis command.

HGETALL myhash
    

This command fetches all fields and their values from the hash named 'myhash'.

Identify Repeating Operations

Look for repeated work inside the command.

• Primary operation: Reading each field and its value in the hash.
• How many times: Once for every field stored in the hash.

How Execution Grows With Input

As the number of fields grows, the work grows too.

Input Size (n)	Approx. Operations
10	About 10 reads
100	About 100 reads
1000	About 1000 reads

Pattern observation: The work grows directly with the number of fields. Double the fields, double the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run HGETALL grows in a straight line with the number of fields in the hash.

Common Mistake

[X] Wrong: "HGETALL is always fast no matter how big the hash is."

[OK] Correct: Because HGETALL reads every field, if the hash is very large, it takes longer. It's not instant for big hashes.

Interview Connect

Understanding how commands like HGETALL scale helps you explain performance clearly and shows you know how data size affects speed.

Self-Check

"What if we used HGET to get only one field instead of HGETALL? How would the time complexity change?"

Practice

1. What does the Redis command HGETALL do when used on a hash key?

easy

A. Returns the number of fields in the hash.

B. Deletes all fields in the hash.

C. Returns only the keys of the hash without values.

D. Returns all fields and their values stored in the hash.

Solution

1. Step 1: Understand the purpose of HGETALL

   The command HGETALL is designed to retrieve all fields and their associated values from a Redis hash key.

2. Step 2: Compare with other commands

   Unlike commands that delete or count fields, HGETALL returns the full content of the hash as field-value pairs.

3. Final Answer:

   Returns all fields and their values stored in the hash. -> Option D

4. Quick Check:

   HGETALL = all fields and values [OK]

Hint: HGETALL always fetches full hash content, fields and values [OK]

Common Mistakes:

• Confusing HGETALL with HDEL which deletes fields
• Thinking HGETALL returns only keys or counts
• Assuming HGETALL returns values without fields

2. Which of the following is the correct syntax to get all fields and values from a Redis hash named user:1000?

easy

A. HGETALL user:1000

B. HGET user:1000 *

C. GETALL user:1000

D. HGETALL(user:1000)

Solution

1. Step 1: Recall Redis command syntax

   Redis commands are written as command name followed by key name without parentheses or extra symbols.

2. Step 2: Identify correct command

   HGETALL user:1000 is the correct syntax to fetch all fields and values from the hash key user:1000.

3. Final Answer:

   HGETALL user:1000 -> Option A

4. Quick Check:

   Correct Redis command syntax = HGETALL key [OK]

Hint: Use HGETALL followed by the hash key name without extra symbols [OK]

Common Mistakes:

• Adding parentheses like a function call
• Using GETALL which is not a Redis command
• Using HGET with wildcard which is invalid

3. Given a Redis hash product:1 with fields and values: {"name": "Pen", "price": "1.5", "stock": "100"}, what will HGETALL product:1 return?

medium

A. ["Pen", "1.5", "100"]

B. ["name", "Pen", "price", "1.5", "stock", "100"]

C. {"name": "Pen", "price": "1.5", "stock": "100"}

D. Error: key does not exist

Solution

1. Step 1: Understand HGETALL output format

   HGETALL returns a flat list of alternating fields and values, not a JSON object.

2. Step 2: Match output to options

   The returned list will be ["name", "Pen", "price", "1.5", "stock", "100"] exactly as in ["name", "Pen", "price", "1.5", "stock", "100"].

3. Final Answer:

   ["name", "Pen", "price", "1.5", "stock", "100"] -> Option B

4. Quick Check:

   HGETALL returns flat list of fields and values [OK]

Hint: HGETALL returns flat list: field, value, field, value... [OK]

Common Mistakes:

• Expecting a JSON object instead of a flat list
• Expecting only values without fields
• Assuming error if key exists

4. You run HGETALL user:2000 but get an empty list []. What could be the reason?

medium

A. HGETALL only returns keys, not values.

B. HGETALL command syntax is incorrect.

C. The hash key user:2000 does not exist or is empty.

D. Redis server is down.

Solution

1. Step 1: Interpret empty list from HGETALL

   An empty list means the hash key does not exist or has no fields stored.

2. Step 2: Eliminate other options

   Syntax error would cause an error message, server down would cause connection failure, and HGETALL returns both keys and values.

3. Final Answer:

   The hash key user:2000 does not exist or is empty. -> Option C

4. Quick Check:

   Empty list means no data for key [OK]

Hint: Empty list means key missing or hash empty [OK]

Common Mistakes:

• Assuming syntax error without checking command
• Thinking server down causes empty list
• Believing HGETALL returns only keys

5. You want to display all user details stored in a Redis hash user:3000 as a JSON object in your application. Which approach correctly uses HGETALL and processes its output?

hard

A. Run HGETALL user:3000, then convert the returned flat list into key-value pairs to form a JSON object.

B. Run HGETALL user:3000 and directly use the returned list as JSON.

C. Run HGET user:3000 * to get all fields as JSON.

D. Run GET user:3000 to get the JSON string.

Solution

1. Step 1: Understand HGETALL output format

   HGETALL returns a flat list alternating fields and values, not a JSON object.

2. Step 2: Convert flat list to JSON object

   To use in an application, convert the list into key-value pairs (e.g., a dictionary) to form a JSON object.

3. Step 3: Eliminate incorrect options

   Run HGETALL user:3000 and directly use the returned list as JSON. is wrong because the list is not JSON. Run HGET user:3000 * to get all fields as JSON. uses invalid syntax. Run GET user:3000 to get the JSON string. assumes the hash is stored as a string.

4. Final Answer:

   Run HGETALL user:3000, then convert the returned flat list into key-value pairs to form a JSON object. -> Option A

5. Quick Check:

   Convert HGETALL list to JSON object before use [OK]

Hint: Convert HGETALL list to key-value pairs for JSON [OK]

Common Mistakes:

• Using HGET with wildcard which is invalid
• Assuming HGETALL returns JSON directly
• Using GET on a hash key expecting JSON