Broadcast joins for small tables in Apache Spark - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a broadcast join in Apache Spark?

A broadcast join is a type of join where a small table is sent (broadcasted) to all worker nodes. This avoids shuffling large data and speeds up the join process.

beginner

Why use broadcast joins for small tables?

Broadcast joins reduce data movement by sending the small table to all nodes. This makes joins faster and more efficient when one table is much smaller than the other.

intermediate

How do you enable a broadcast join in Spark using DataFrame API?

You can use the function broadcast() from pyspark.sql.functions to mark a small DataFrame for broadcasting before joining it with a large DataFrame.

intermediate

What happens if you broadcast a large table by mistake?

Broadcasting a large table can cause memory issues on worker nodes and slow down the job because the large data is sent to all nodes, defeating the purpose of optimization.

intermediate

How does Spark decide to use broadcast join automatically?

Spark uses a configuration called spark.sql.autoBroadcastJoinThreshold to decide the max size of a table to broadcast automatically during joins.

What is the main benefit of a broadcast join in Spark?

A Reduces data shuffling by sending small table to all nodes

B Increases data shuffling for better parallelism

C Broadcasts large tables to reduce memory usage

D Avoids joins altogether

Broadcast joins reduce data shuffling by sending the small table to all worker nodes, speeding up the join.

Which Spark function is used to mark a DataFrame for broadcast join?

A persist()

B cache()

C broadcast()

D collect()

The broadcast() function marks a DataFrame to be broadcasted to all nodes for join.

What configuration controls the max size of a table to broadcast automatically?

A spark.executor.memory

B spark.sql.shuffle.partitions

C spark.sql.broadcastTimeout

D spark.sql.autoBroadcastJoinThreshold

spark.sql.autoBroadcastJoinThreshold sets the max size for automatic broadcast joins.

What is a risk of broadcasting a large table?

A Faster join execution

B Memory overflow on worker nodes

C Reduced network traffic

D Automatic caching

Broadcasting large tables can cause memory overflow and slow down the job.

When should you prefer broadcast join?

A When one table is much smaller than the other

B When both tables are very large

C When tables have no common keys

D When you want to avoid joins

Broadcast joins are best when one table is small enough to send to all nodes.

Explain how broadcast joins improve join performance in Spark.

Think about how sending small data to all workers helps avoid moving large data around.

Describe how to use broadcast join in Spark with code.

Recall the function name and how it is used in DataFrame joins.

Practice

1.

What is the main benefit of using broadcast() in Spark when joining tables?

easy

A. It compresses the large table to save memory.

B. It sorts both tables before joining.

C. It sends the small table to all worker nodes to speed up the join.

D. It duplicates the large table across all nodes.

Solution

1. Step 1: Understand broadcast join purpose

   Broadcast join sends the small table to all worker nodes to avoid shuffling the large table.

2. Step 2: Identify the benefit

   This reduces network data movement and speeds up the join operation.

3. Final Answer:

   It sends the small table to all worker nodes to speed up the join. -> Option C

4. Quick Check:

   Broadcast join = send small table to all nodes [OK]

Hint: Broadcast small table to all nodes to avoid shuffle [OK]

Common Mistakes:

• Thinking broadcast compresses large table
• Assuming broadcast sorts tables
• Believing broadcast duplicates large table

2.

Which of the following is the correct syntax to broadcast a small DataFrame small_df in Spark before joining?

from pyspark.sql.functions import broadcast

result = large_df.join(____, 'id')

easy

A. small_df.join(broadcast())

B. small_df.broadcast()

C. broadcast(large_df)

D. broadcast(small_df)

Solution

1. Step 1: Recall broadcast syntax

   In Spark, you use broadcast() function around the small DataFrame to mark it for broadcasting.

2. Step 2: Apply to join

   The join should be large_df.join(broadcast(small_df), 'id') to broadcast the small table.

3. Final Answer:

   broadcast(small_df) -> Option D

4. Quick Check:

   Use broadcast() function on small_df [OK]

Hint: Use broadcast() around small DataFrame in join [OK]

Common Mistakes:

• Calling broadcast as a method on DataFrame
• Broadcasting the large DataFrame instead
• Incorrect join syntax with broadcast

3.

Given the following Spark code, what will be the output count?

from pyspark.sql import SparkSession
from pyspark.sql.functions import broadcast

spark = SparkSession.builder.getOrCreate()

large_data = [(1, 'A'), (2, 'B'), (3, 'C')]
small_data = [(1, 'X'), (2, 'Y')]

large_df = spark.createDataFrame(large_data, ['id', 'val1'])
small_df = spark.createDataFrame(small_data, ['id', 'val2'])

joined_df = large_df.join(broadcast(small_df), 'id')
print(joined_df.count())

medium

A. 2

B. 5

C. 3

D. 0

Solution

1. Step 1: Analyze join keys and data

   large_df has ids 1, 2, 3; small_df has ids 1, 2. Join on 'id' keeps only matching ids.

2. Step 2: Count matching rows

   Ids 1 and 2 match in both tables, so joined_df has 2 rows.

3. Final Answer:

   2 -> Option A

4. Quick Check:

   Join count = matching ids = 2 [OK]

Hint: Count matching keys in both tables after join [OK]

Common Mistakes:

• Counting all rows from large_df ignoring join
• Assuming broadcast changes join result count
• Counting unmatched rows

4.

Identify the error in the following Spark code that attempts a broadcast join:

from pyspark.sql.functions import broadcast

result = large_df.join(small_df.broadcast(), 'id')

medium

A. Missing import for broadcast function.

B. Using broadcast as a method on DataFrame is incorrect.

C. Join key 'id' does not exist in both DataFrames.

D. Broadcasting large_df instead of small_df.

Solution

1. Step 1: Check broadcast usage

   Broadcast is a function, not a method on DataFrame, so small_df.broadcast() is invalid syntax.

2. Step 2: Correct usage

   Use broadcast(small_df) instead to mark small_df for broadcasting.

3. Final Answer:

   Using broadcast as a method on DataFrame is incorrect. -> Option B

4. Quick Check:

   broadcast() is a function, not a DataFrame method [OK]

Hint: Use broadcast() function, not DataFrame.broadcast() [OK]

Common Mistakes:

• Calling broadcast as a DataFrame method
• Ignoring import of broadcast function
• Confusing which DataFrame to broadcast

5.

You have a large DataFrame orders with millions of rows and a small DataFrame countries with 10 rows. You want to join them on country_code. Which approach will give the best performance?

hard

A. Use orders.join(broadcast(countries), 'country_code') to broadcast the small table.

B. Use orders.join(countries, 'country_code') without broadcasting.

C. Broadcast the large orders DataFrame instead.

D. Collect both DataFrames to driver and join locally.

Solution

1. Step 1: Identify table sizes

   Since countries is small, broadcasting it avoids shuffling the large orders DataFrame.

2. Step 2: Choose best join method

   Broadcast join sends the small table to all nodes, speeding up the join and reducing network traffic.

3. Final Answer:

   Use orders.join(broadcast(countries), 'country_code') to broadcast the small table. -> Option A

4. Quick Check:

   Broadcast small table for best join performance [OK]

Hint: Broadcast the small table in large-small joins [OK]

Common Mistakes:

• Broadcasting the large DataFrame wastes memory
• Not broadcasting causes expensive shuffle
• Collecting large data to driver causes failure