Why data format affects performance in Apache Spark - Quick Recap

Recall & Review

beginner

What is a data format in the context of Apache Spark?

A data format is the way data is stored and organized on disk or in memory, such as CSV, JSON, Parquet, or ORC. It affects how Spark reads and writes data.

beginner

Why does using a columnar data format like Parquet improve performance in Spark?

Columnar formats store data by columns, so Spark can read only the needed columns, reducing disk I/O and speeding up queries.

intermediate

How does compression in data formats affect Spark performance?

Compression reduces file size, lowering disk and network usage. However, decompressing data uses CPU, so the right balance improves overall speed.

intermediate

What is predicate pushdown and how does it relate to data formats?

Predicate pushdown lets Spark filter data early during reading, reducing data scanned. Formats like Parquet and ORC support this, improving performance.

beginner

Why might JSON or CSV formats be slower than Parquet in Spark?

JSON and CSV are row-based and text formats, requiring more parsing and reading all data even if only some columns are needed, making them slower.

Which data format is typically fastest for analytical queries in Spark?

A JSON

B CSV

C Parquet

D TXT

Parquet is a columnar format optimized for analytical queries, making it faster than CSV, JSON, or plain text.

What feature allows Spark to read only necessary columns from a dataset?

A Predicate pushdown

B Column pruning

C Compression

D Partitioning

Column pruning lets Spark read only the columns needed, reducing data read and improving speed.

How does compression affect Spark's data processing?

A Reduces file size but may add CPU overhead

B Always slows down processing

C Increases file size

D Has no effect

Compression reduces file size, saving disk and network time, but decompressing uses CPU, so it can speed up or slow down depending on balance.

Which data format supports predicate pushdown in Spark?

A Parquet

B CSV

C JSON

D TXT

Parquet supports predicate pushdown, allowing Spark to filter data early and improve performance.

Why is reading JSON slower than Parquet in Spark?

A JSON is binary format

B JSON files are always compressed

C JSON supports column pruning

D JSON requires parsing text and reads all data

JSON is a text format that requires parsing and does not support column pruning, so Spark reads all data, making it slower.

Explain how data format choice affects Spark query performance.

Think about how Spark reads data and what features help reduce work.

Describe why Parquet is often preferred over CSV or JSON for big data analytics in Spark.

Focus on how Parquet saves time and resources during queries.

Practice

1. Why does using a columnar data format like Parquet improve performance in Apache Spark?

easy

A. Because it converts all data into JSON format for easy parsing.

B. Because it compresses data into a single large file without structure.

C. Because it stores data by columns, allowing faster reads of specific columns.

D. Because it stores data as plain text for better compatibility.

Solution

1. Step 1: Understand columnar storage

   Columnar formats store data by columns, not rows, so Spark reads only needed columns.

2. Step 2: Impact on performance

   Reading fewer columns reduces disk I/O and speeds up queries.

3. Final Answer:

   Because it stores data by columns, allowing faster reads of specific columns. -> Option C

4. Quick Check:

   Columnar storage = faster column reads [OK]

Hint: Columnar = faster column access, less data read [OK]

Common Mistakes:

• Thinking all formats compress data the same way
• Confusing row-based with column-based storage
• Assuming JSON is always faster due to readability

2. Which of the following is the correct way to read a Parquet file in Apache Spark using PySpark?

easy

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

B. spark.read.csv('data.parquet')

C. spark.load('data.parquet')

D. spark.read.json('data.parquet')

Solution

1. Step 1: Recall Spark read syntax

   Spark uses spark.read.format() or shortcut methods like parquet() to read files.

2. Step 2: Identify correct method for Parquet

   spark.read.parquet() is the correct method to read Parquet files.

3. Final Answer:

   spark.read.parquet('data.parquet') -> Option A

4. Quick Check:

   Use spark.read.parquet() for Parquet files [OK]

Hint: Use spark.read.parquet() to read Parquet files [OK]

Common Mistakes:

• Using csv() or json() methods for Parquet files
• Trying to use spark.load() which is invalid
• Confusing file format with method name

3. Given the following PySpark code, what will be the output type of df.count() when reading a Parquet file?

df = spark.read.parquet('data.parquet')
count = df.count()

medium

A. A DataFrame containing the count

B. An integer representing the number of rows

C. A string describing the count

D. A list of counts per column

Solution

1. Step 1: Understand df.count() method

   The count() method returns the total number of rows as an integer.

2. Step 2: Confirm output type

   Since count() returns a number, the output is an integer, not a DataFrame or list.

3. Final Answer:

   An integer representing the number of rows -> Option B

4. Quick Check:

   df.count() returns integer row count [OK]

Hint: count() returns integer row count [OK]

Common Mistakes:

• Expecting count() to return a DataFrame
• Thinking count() returns a string or list
• Confusing count() with collect()

4. You try to read a JSON file with spark.read.parquet('data.json') and get an error. What is the most likely cause?

medium

A. Spark cannot read any file formats other than Parquet

B. The file path is incorrect

C. The JSON file is empty

D. You are using the wrong read method for the file format

Solution

1. Step 1: Identify file format mismatch

   The code uses read.parquet() on a JSON file, which causes a format error.

2. Step 2: Correct method for JSON files

   Use spark.read.json() to read JSON files correctly.

3. Final Answer:

   You are using the wrong read method for the file format -> Option D

4. Quick Check:

   Use matching read method for file format [OK]

Hint: Match read method to file format (json, parquet, csv) [OK]

Common Mistakes:

• Assuming file path is always the problem
• Thinking Spark only reads Parquet files
• Ignoring file format when reading data

5. You have a large dataset stored as CSV and want to improve query speed in Spark. Which approach best improves performance while minimizing storage size?

hard

A. Convert CSV to Parquet format and use Spark SQL queries

B. Keep CSV but compress files with gzip

C. Convert CSV to JSON format for better readability

D. Split CSV into many small files without changing format

Solution

1. Step 1: Understand format impact on performance

   Parquet is columnar and compressed, improving query speed and reducing storage.

2. Step 2: Compare alternatives

   Compressing CSV helps storage but not query speed; JSON is slower; many small files hurt performance.

3. Final Answer:

   Convert CSV to Parquet format and use Spark SQL queries -> Option A

4. Quick Check:

   Parquet = faster queries + smaller size [OK]

Hint: Convert to Parquet for speed and compression [OK]

Common Mistakes:

• Thinking compression alone speeds queries
• Choosing JSON for performance
• Splitting files without format change improves speed