Unit testing Spark transformations in Apache Spark - Time & Space Complexity

Time Complexity: Unit testing Spark transformations

O(n)

Understanding Time Complexity

When we test Spark transformations, we want to know how the time to run tests grows as data grows.

We ask: How does the test execution time change when input data size increases?

Scenario Under Consideration

Analyze the time complexity of the following Spark transformation test code.

from pyspark.sql import SparkSession

spark = SparkSession.builder.getOrCreate()

input_df = spark.createDataFrame([(1, "a"), (2, "b")], ["id", "value"])

result_df = input_df.filter(input_df.id > 1).select("value")

assert result_df.count() == 1

This code creates a small DataFrame, applies a filter and select transformation, then checks the count.

Identify Repeating Operations

Look at what repeats when the input grows.

• Primary operation: The filter and select run on each row of the input DataFrame.
• How many times: Once per row, so as many times as there are rows (n).

How Execution Grows With Input

As input rows increase, the number of operations grows roughly the same.

Input Size (n)	Approx. Operations
10	About 10 filter checks and selects
100	About 100 filter checks and selects
1000	About 1000 filter checks and selects

Pattern observation: The work grows directly with the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the test time grows linearly as the input data size grows.

Common Mistake

[X] Wrong: "Unit tests run instantly no matter how big the data is."

[OK] Correct: Even tests run transformations on all rows, so bigger data means more work and longer test time.

Interview Connect

Understanding how test time grows helps you write tests that stay fast and reliable as data grows.

Self-Check

"What if we cache the DataFrame before filtering? How would the time complexity change?"

Practice

1. What is the main purpose of unit testing Spark transformations?

easy

A. To check small parts of Spark code for errors early

B. To improve the speed of Spark jobs

C. To deploy Spark applications automatically

D. To visualize Spark data outputs

Solution

1. Step 1: Understand unit testing purpose

   Unit testing focuses on checking small parts of code to find errors early.

2. Step 2: Relate to Spark transformations

   Testing Spark transformations means verifying each step works correctly before full runs.

3. Final Answer:

   To check small parts of Spark code for errors early -> Option A

4. Quick Check:

   Unit testing = Early error detection [OK]

Hint: Unit tests catch errors early in small code parts [OK]

Common Mistakes:

• Confusing unit testing with performance tuning
• Thinking unit tests deploy code
• Assuming unit tests create visualizations

2. Which of the following is the correct way to compare actual and expected DataFrames in a Spark unit test?

easy

A. print(actual_df) == print(expected_df)

B. assert actual_df.collect() == expected_df.collect()

C. actual_df.show() == expected_df.show()

D. actual_df.count() != expected_df.count()

Solution

1. Step 1: Understand DataFrame comparison

   Comparing DataFrames requires checking their collected data, not just printing or counts.

2. Step 2: Identify correct assertion

   Using assert with collected rows compares actual data content correctly.

3. Final Answer:

   assert actual_df.collect() == expected_df.collect() -> Option B

4. Quick Check:

   Compare collected data for equality [OK]

Hint: Use collect() to compare DataFrame contents in tests [OK]

Common Mistakes:

• Comparing printed output instead of data
• Using show() which returns None
• Comparing only row counts without data

3. Given the following Spark code in a unit test:

input_df = spark.createDataFrame([(1, 'a'), (2, 'b')], ['id', 'value'])
transformed_df = input_df.filter("id > 1")
result = transformed_df.collect()

What is the value of result?

medium

A. [Row(id=1, value='a')]

B. []

C. [Row(id=1, value='a'), Row(id=2, value='b')]

D. [Row(id=2, value='b')]

Solution

1. Step 1: Understand the filter condition

   The filter "id > 1" keeps rows where id is greater than 1, so only id=2 remains.

2. Step 2: Collect the filtered rows

   Collect returns a list of Row objects matching the filter, here only one row with id=2 and value='b'.

3. Final Answer:

   [Row(id=2, value='b')] -> Option D

4. Quick Check:

   Filter id > 1 keeps only id=2 [OK]

Hint: Filter keeps rows matching condition before collect [OK]

Common Mistakes:

• Including rows with id=1 mistakenly
• Confusing collect output format
• Assuming filter excludes id=2

4. You wrote this unit test code:

expected_df = spark.createDataFrame([(1, 'x')], ['id', 'value'])
actual_df = spark.createDataFrame([(1, 'x')], ['id', 'value'])
assert expected_df == actual_df

Why does this test fail?

medium

A. DataFrames cannot be compared directly with '=='

B. The schemas of DataFrames are different

C. The data in DataFrames is different

D. Spark session is not initialized

Solution

1. Step 1: Understand DataFrame equality

   Spark DataFrames do not support direct '==' comparison; it checks object identity, not content.

2. Step 2: Correct way to compare DataFrames

   Use methods like collect() or exceptAll() to compare data content, not '=='.

3. Final Answer:

   DataFrames cannot be compared directly with '==' -> Option A

4. Quick Check:

   Use collect() for DataFrame equality, not '==' [OK]

Hint: Never use '==' to compare DataFrames directly [OK]

Common Mistakes:

• Assuming '==' compares data content
• Ignoring schema differences
• Forgetting to initialize Spark session

5. You want to unit test a Spark transformation that removes duplicate rows based on the 'id' column, keeping the first occurrence. Which approach correctly tests this transformation?

hard

A. Create input DataFrame without duplicates, apply transformation, assert output equals input

B. Create input DataFrame with duplicates, apply transformation, assert output count equals input count

C. Create input DataFrame with duplicates, apply transformation, assert output equals expected DataFrame without duplicates

D. Create input DataFrame with duplicates, apply transformation, assert output is empty

Solution

1. Step 1: Prepare input with duplicates

   To test duplicate removal, input must contain duplicate rows on 'id'.

2. Step 2: Apply transformation and compare output

   After transformation, output should have duplicates removed; compare with expected DataFrame without duplicates.

3. Final Answer:

   Create input DataFrame with duplicates, apply transformation, assert output equals expected DataFrame without duplicates -> Option C

4. Quick Check:

   Test removes duplicates by comparing expected output [OK]

Hint: Test duplicate removal by comparing to expected no-duplicate DataFrame [OK]

Common Mistakes:

• Testing with no duplicates in input
• Comparing only row counts, not content
• Expecting empty output after removal