Why Data serialization (Avro, Parquet, ORC) in Hadoop? - Purpose & Use Cases

The Big Idea

What if you could turn messy data chaos into lightning-fast insights with just a few clicks?

The Scenario

Imagine you have a huge pile of data files in different formats scattered all over your computer. You want to analyze them quickly, but each file is stored differently, and you have to open each one manually to understand its structure and content.

The Problem

Manually opening and converting each file is slow and tiring. It's easy to make mistakes, like mixing up data types or losing information. Also, reading large files without a standard format wastes time and computer power.

The Solution

Data serialization formats like Avro, Parquet, and ORC organize data in a smart, consistent way. They compress data efficiently and keep its structure clear. This makes reading, writing, and sharing data fast and reliable, even with huge datasets.

Before vs After

✗ Before

open('data.txt')
read line by line
parse manually

✓ After

spark.read.parquet('data.parquet')
.show()

What It Enables

It lets you handle massive data quickly and accurately, unlocking powerful analysis and faster decisions.

Real Life Example

A company collects millions of customer records daily. Using Parquet files, they store data compactly and query it instantly to understand buying trends and improve services.

Key Takeaways

Manual data handling is slow and error-prone.

Serialization formats standardize and compress data efficiently.

This leads to faster, reliable data processing at scale.

Practice

1. Which data serialization format stores data in a row-wise manner and includes a schema for each record?

easy

A. Avro

B. Parquet

C. ORC

D. CSV

Solution

1. Step 1: Understand Avro's storage method

   Avro stores data row-wise, meaning it saves one record at a time along with its schema.

2. Step 2: Compare with other formats

   Parquet and ORC store data column-wise, optimizing for query speed, while CSV has no schema.

3. Final Answer:

   Avro -> Option A

4. Quick Check:

   Row-wise with schema = Avro [OK]

Hint: Row-wise + schema means Avro format [OK]

Common Mistakes:

• Confusing Parquet or ORC as row-wise
• Thinking CSV has schema
• Mixing storage orientation concepts

2. Which of the following is the correct way to specify a Parquet file format in a Hadoop job configuration?

easy

A. job.setOutputFormatClass(TextOutputFormat.class);

B. job.setOutputFormatClass(AvroOutputFormat.class);

C. job.setOutputFormatClass(OrcOutputFormat.class);

D. job.setOutputFormatClass(ParquetOutputFormat.class);

Solution

1. Step 1: Identify the output format class for Parquet

   Parquet files require setting the output format to ParquetOutputFormat in Hadoop jobs.

2. Step 2: Eliminate other options

   TextOutputFormat is for text files, AvroOutputFormat for Avro files, and OrcOutputFormat for ORC files.

3. Final Answer:

   job.setOutputFormatClass(ParquetOutputFormat.class); -> Option D

4. Quick Check:

   Parquet output format = ParquetOutputFormat [OK]

Hint: Parquet uses ParquetOutputFormat class in Hadoop [OK]

Common Mistakes:

• Using TextOutputFormat for Parquet files
• Confusing AvroOutputFormat with ParquetOutputFormat
• Mixing ORC and Parquet output formats

3. Given the following PySpark code snippet, what will be the output schema of the saved file?

df.write.format('orc').save('/data/output')

medium

A. Data saved in ORC format with schema preserved

B. Data saved in CSV format without schema

C. Data saved in Parquet format with schema preserved

D. Data saved in Avro format with schema preserved

Solution

1. Step 1: Identify the format used in the code

   The code uses df.write.format('orc'), which means data is saved in ORC format.

2. Step 2: Understand ORC properties

   ORC stores data column-wise and preserves schema for efficient queries.

3. Final Answer:

   Data saved in ORC format with schema preserved -> Option A

4. Quick Check:

   ORC format with schema = Data saved in ORC format with schema preserved [OK]

Hint: format('orc') means ORC with schema saved [OK]

Common Mistakes:

• Assuming default is CSV
• Confusing ORC with Parquet or Avro
• Ignoring schema preservation in ORC

4. You try to read a Parquet file in Spark using this code:

spark.read.format('parquet').load('/data/file.orc')

What is the main issue here?

medium

A. File extension does not match format specified

B. Parquet format cannot read ORC files

C. Spark cannot read Parquet files

D. No issue, code will run fine

Solution

1. Step 1: Check the file format and extension

   The code tries to read a file with .orc extension using Parquet format.

2. Step 2: Understand format compatibility

   Parquet reader cannot read ORC files because they have different internal structures.

3. Final Answer:

   Parquet format cannot read ORC files -> Option B

4. Quick Check:

   Parquet reader ≠ ORC file [OK]

Hint: Parquet reader can't read ORC files [OK]

Common Mistakes:

• Ignoring file extension mismatch
• Assuming Spark auto-detects format
• Thinking Parquet and ORC are interchangeable

5. You have a large dataset with many columns but only a few are needed for analysis. Which data serialization format is best to optimize query speed and storage, and why?

hard

A. CSV, because it is simple and easy to read

B. Avro, because it stores data row-wise with schema

C. Parquet, because it stores data column-wise allowing fast column queries

D. JSON, because it supports nested data

Solution

1. Step 1: Understand the dataset and query needs

   Many columns exist but only a few are needed, so reading only those columns is important.

2. Step 2: Compare serialization formats for columnar access

   Parquet stores data column-wise, enabling fast queries on selected columns and saving storage.

3. Step 3: Eliminate other options

   Avro is row-wise, so it reads all columns; CSV and JSON lack efficient columnar storage and schema.

4. Final Answer:

   Parquet, because it stores data column-wise allowing fast column queries -> Option C

5. Quick Check:

   Column-wise storage = Parquet best for selective queries [OK]

Hint: Column-wise format like Parquet speeds up column queries [OK]

Common Mistakes:

• Choosing Avro for column queries
• Picking CSV or JSON for big data efficiency
• Ignoring storage and query speed trade-offs