Pig vs Hive comparison in Hadoop - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to load data in Pig Latin.

Hadoop

data = LOAD 'input.txt' USING [1] AS (name:chararray, age:int);

Drag options to blanks, or click blank then click option'

AHiveStorage

BPigStorage(',')

CTextLoader

DJsonLoader

Attempts:

3 left

💡 Hint

Common Mistakes

Using HiveStorage in Pig script.

Using JsonLoader for plain text files.

In Pig, PigStorage is used to load data from text files with a delimiter.

2fill in blank

medium

Complete the Hive query to select all records from a table.

Hadoop

SELECT * FROM [1];

Drag options to blanks, or click blank then click option'

Adatabase

Bview

Ccolumn

Dtable_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using database name instead of table name.

Using column name in FROM clause.

In Hive, you select data from a table, not a database or column directly.

3fill in blank

hard

Fix the error in the Pig script to filter records where age is greater than 30.

Hadoop

filtered = FILTER data BY age [1] 30;

Drag options to blanks, or click blank then click option'

A=

B==

C>

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using == instead of >.

Using = which is assignment, not comparison.

In Pig Latin, the correct operator for 'greater than' is >.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension in Python that filters words longer than 3 characters.

Hadoop

lengths = {word: [1] for word in words if len(word) [2] 3}

Drag options to blanks, or click blank then click option'

Alen(word)

B>

C<

Dword

Attempts:

3 left

💡 Hint

Common Mistakes

Using < instead of > in the condition.

Using word instead of len(word) for the value.

The dictionary comprehension maps each word to its length if the length is greater than 3.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps uppercase keys to values greater than 0.

Hadoop

result = { [1]: [2] for k, v in data.items() if v [3] 0 }

Drag options to blanks, or click blank then click option'

Ak.upper()

Bv

C>

Dk.lower()

Attempts:

3 left

💡 Hint

Common Mistakes

Using k.lower() instead of k.upper().

Using < instead of > in the condition.

This comprehension creates a dictionary with uppercase keys and values only if the value is greater than zero.

Practice

1. Which statement best describes the main difference between Pig and Hive in Hadoop?

easy

A. Pig stores data, Hive processes data.

B. Pig is declarative, and Hive is procedural.

C. Pig is used only for batch processing, Hive only for real-time.

D. Pig uses a scripting language, while Hive uses SQL-like queries.

Solution

1. Step 1: Understand Pig and Hive languages

   Pig uses a scripting language called Pig Latin, which is procedural. Hive uses a SQL-like declarative language called HiveQL.

2. Step 2: Compare their query styles

   Pig scripts describe how to process data step-by-step (procedural), while Hive queries describe what data to retrieve (declarative).

3. Final Answer:

   Pig uses a scripting language, while Hive uses SQL-like queries. -> Option D

4. Quick Check:

   Language style difference = Pig scripting, Hive SQL [OK]

Hint: Pig = scripting; Hive = SQL-like queries [OK]

Common Mistakes:

• Confusing procedural and declarative terms
• Thinking Pig uses SQL
• Assuming Hive is procedural

2. Which of the following is the correct way to write a simple query in Hive to select all records from a table named users?

easy

A. SELECT * FROM users;

B. LOAD users;

C. FETCH ALL FROM users;

D. GET * FROM users;

Solution

1. Step 1: Recall Hive query syntax

   Hive uses SQL-like syntax. The standard way to select all records is SELECT * FROM table_name;.

2. Step 2: Check each option

   SELECT * FROM users; matches the correct SQL syntax. Options A, C, and D are not valid Hive commands.

3. Final Answer:

   SELECT * FROM users; -> Option A

4. Quick Check:

   Hive uses SQL syntax = SELECT * FROM [table] [OK]

Hint: Hive queries look like standard SQL SELECT statements [OK]

Common Mistakes:

• Using non-SQL keywords like LOAD or FETCH for queries
• Forgetting the FROM keyword
• Using GET instead of SELECT

3. Given the following Pig script:

data = LOAD 'input' AS (name:chararray, age:int);
filtered = FILTER data BY age > 25;
DUMP filtered;

What will be the output if the input data contains:

('Alice', 30)
('Bob', 22)
('Carol', 27)

medium

A. All three records

B. ('Bob', 22) only

C. ('Alice', 30) and ('Carol', 27)

D. No output

Solution

1. Step 1: Understand the FILTER condition

   The script filters records where age is greater than 25.

2. Step 2: Apply filter to input data

   'Alice' (30) and 'Carol' (27) satisfy age > 25; 'Bob' (22) does not.

3. Final Answer:

   ('Alice', 30) and ('Carol', 27) -> Option C

4. Quick Check:

   Filter age > 25 = Alice and Carol [OK]

Hint: Filter keeps only records matching condition [OK]

Common Mistakes:

• Including records with age equal to 25
• Confusing FILTER with LOAD
• Assuming all records are output

4. Identify the error in this Hive query:

SELECT name age FROM users WHERE age > 20;

medium

A. Missing comma between selected columns.

B. Incorrect WHERE clause syntax.

C. Table name should be in quotes.

D. SELECT keyword is misspelled.

Solution

1. Step 1: Analyze the SELECT clause

   The query selects two columns: name and age. They must be separated by a comma.

2. Step 2: Check the query syntax

   The query misses a comma between 'name' and 'age'. The WHERE clause and table name are correct.

3. Final Answer:

   Missing comma between selected columns. -> Option A

4. Quick Check:

   Columns in SELECT need commas [OK]

Hint: Separate columns with commas in SELECT [OK]

Common Mistakes:

• Omitting commas between columns
• Adding quotes around table names unnecessarily
• Miswriting WHERE clause

5. You want to process a complex data flow involving multiple steps of filtering, grouping, and joining large datasets in Hadoop. Which tool is better suited and why?

hard

A. Hive, because it uses SQL and is easier for complex flows.

B. Pig, because it supports procedural scripting for complex data flows.

C. Hive, because it is procedural and faster for joins.

D. Pig, because it only supports simple queries.

Solution

1. Step 1: Understand tool strengths

   Pig is procedural and designed for complex data flows with multiple steps. Hive is declarative and better for simple querying.

2. Step 2: Match tool to task

   For complex filtering, grouping, and joining in multiple steps, Pig's scripting is more flexible and suitable.

3. Final Answer:

   Pig, because it supports procedural scripting for complex data flows. -> Option B

4. Quick Check:

   Complex flows = Pig scripting [OK]

Hint: Use Pig for complex multi-step data processing [OK]

Common Mistakes:

• Choosing Hive for complex procedural flows
• Thinking Pig only supports simple queries
• Confusing procedural and declarative