Data serialization (Avro, Parquet, ORC) in Hadoop - Time & Space Complexity

Time Complexity: Data serialization (Avro, Parquet, ORC)

O(n)

Understanding Time Complexity

When working with big data, we often save data in special formats like Avro, Parquet, or ORC. Understanding how long it takes to read or write these formats helps us plan and speed up data processing.

We want to know: how does the time to serialize or deserialize data grow as the data size grows?

Scenario Under Consideration

Analyze the time complexity of the following Hadoop code snippet that writes data using Parquet format.

    Job job = Job.getInstance(conf);
    job.setOutputFormatClass(ParquetOutputFormat.class);
    ParquetOutputFormat.setWriteSupportClass(job, AvroWriteSupport.class);
    ParquetOutputFormat.setCompression(job, CompressionCodecName.SNAPPY);
    
    // Mapper writes records to Parquet files
    public void map(LongWritable key, Text value, Context context) throws IOException, InterruptedException {
        // Convert input to Avro record
        // Write record to ParquetOutputFormat
        context.write(null, avroRecord);
    }
    

This code writes many records into Parquet files using Avro schema inside Hadoop MapReduce.

Identify Repeating Operations

Look for repeated actions that take most time.

• Primary operation: Writing each record to the Parquet file inside the map function.
• How many times: Once for every input record, so the number of records (n).

How Execution Grows With Input

As the number of records grows, the time to write grows too.

Input Size (n)	Approx. Operations
10	10 writes
100	100 writes
1000	1000 writes

Pattern observation: The time grows roughly in direct proportion to the number of records.

Final Time Complexity

Time Complexity: O(n)

This means the time to serialize data grows linearly with the number of records.

Common Mistake

[X] Wrong: "Serialization time stays the same no matter how much data we write."

[OK] Correct: Each record must be processed and written, so more data means more work and more time.

Interview Connect

Knowing how serialization time grows helps you explain data pipeline speed and design better systems. It shows you understand how data size affects processing time.

Self-Check

"What if we changed from writing data record-by-record to writing in batches? How would the time complexity change?"

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