Adaptive query execution in Apache Spark

Introduction

Adaptive query execution helps Spark run queries faster by changing the plan while the query is running. It fixes problems like wrong data size guesses to make the work easier and quicker.

When you run big data queries and don't know the exact size of data beforehand.

When your query has joins and the data distribution is uneven or changes.

When you want Spark to automatically optimize shuffle partitions for better speed.

When you want to avoid manual tuning of query plans for different datasets.

Syntax

Apache Spark

spark.conf.set("spark.sql.adaptive.enabled", "true")

This setting turns on adaptive query execution in Spark.

You usually set this before running your Spark SQL queries.

Examples

Enable adaptive query execution and run a join query. Spark will adjust the join strategy during execution.

Apache Spark

spark.conf.set("spark.sql.adaptive.enabled", "true")
spark.sql("SELECT * FROM table1 JOIN table2 ON table1.id = table2.id").show()

Turn off adaptive query execution to see the difference in performance or behavior.

Apache Spark

spark.conf.set("spark.sql.adaptive.enabled", "false")
# Run query without adaptive execution

Sample Program

This code creates two small tables and joins them with adaptive query execution enabled. Spark can optimize the join during runtime for better performance.

Apache Spark

from pyspark.sql import SparkSession

# Create Spark session
spark = SparkSession.builder.appName("AdaptiveQueryExecutionExample").getOrCreate()

# Enable adaptive query execution
spark.conf.set("spark.sql.adaptive.enabled", "true")

# Create sample data
data1 = [(1, "Alice"), (2, "Bob"), (3, "Charlie")]
data2 = [(1, "HR"), (2, "Finance"), (4, "Marketing")]

# Create DataFrames
df1 = spark.createDataFrame(data1, ["id", "name"])
df2 = spark.createDataFrame(data2, ["id", "department"])

# Register as temp views
df1.createOrReplaceTempView("employees")
df2.createOrReplaceTempView("departments")

# Run join query
result = spark.sql("""
SELECT e.id, e.name, d.department
FROM employees e
JOIN departments d ON e.id = d.id
""")

# Show result
result.show()

# Stop Spark session
spark.stop()

Important Notes

Adaptive query execution works best with Spark SQL and DataFrame APIs.

It can change join types, shuffle partitions, and skew handling automatically.

Make sure your Spark version supports adaptive query execution (Spark 3.0+).

Summary

Adaptive query execution lets Spark improve query speed by changing plans while running.

Enable it by setting spark.sql.adaptive.enabled to true.

It helps especially with joins and big data where sizes are unknown or uneven.

Practice

1.

What is the main purpose of adaptive query execution in Apache Spark?

easy

A. To improve query performance by adjusting the execution plan during runtime

B. To statically compile queries before execution

C. To disable query optimization for faster execution

D. To manually rewrite queries for better speed

Solution

1. Step 1: Understand adaptive query execution concept

   Adaptive query execution allows Spark to change the query plan dynamically while the query runs.

2. Step 2: Identify the main benefit

   This dynamic adjustment improves performance by optimizing joins and data shuffles based on actual data size.

3. Final Answer:

   To improve query performance by adjusting the execution plan during runtime -> Option A

4. Quick Check:

   Adaptive query execution = dynamic plan adjustment [OK]

Hint: Think: adaptive means changing during execution [OK]

Common Mistakes:

• Confusing adaptive execution with static query compilation
• Believing it disables optimization
• Thinking it requires manual query rewriting

2.

Which Spark configuration enables adaptive query execution?

?

easy

A. spark.sql.execution.adaptive.enabled = false

B. spark.execution.adaptive = true

C. spark.adaptive.query.execution = true

D. spark.sql.adaptive.enabled = true

Solution

1. Step 1: Recall the exact configuration key

   The correct key to enable adaptive query execution is spark.sql.adaptive.enabled.

2. Step 2: Confirm the value to enable

   Setting it to true activates adaptive query execution.

3. Final Answer:

   spark.sql.adaptive.enabled = true -> Option D

4. Quick Check:

   Enable adaptive query with spark.sql.adaptive.enabled [OK]

Hint: Remember full key: spark.sql.adaptive.enabled [OK]

Common Mistakes:

• Using incorrect config keys like spark.execution.adaptive
• Setting the value to false instead of true
• Mixing up config names with similar words

3.

Given the following Spark SQL code with adaptive query execution enabled, what will be the effect on the join?

spark.conf.set("spark.sql.adaptive.enabled", "true")

val df1 = spark.range(1000)
val df2 = spark.range(10)

val joined = df1.join(df2, df1("id") === df2("id"))
joined.explain(true)

What does adaptive query execution do here?

medium

A. It converts the join to a broadcast join because df2 is small

B. It disables the join optimization and runs a shuffle join

C. It throws an error because adaptive execution cannot handle joins

D. It caches both dataframes before joining

Solution

1. Step 1: Identify adaptive execution behavior on join

   Adaptive query execution detects small tables and converts joins to broadcast joins to reduce shuffle.

2. Step 2: Analyze data sizes in example

   df2 has only 10 rows, which is small enough to broadcast.

3. Final Answer:

   It converts the join to a broadcast join because df2 is small -> Option A

4. Quick Check:

   Small table join = broadcast join [OK]

Hint: Small table in join? Adaptive broadcasts it [OK]

Common Mistakes:

• Assuming adaptive disables optimization
• Thinking adaptive causes errors on joins
• Believing it caches dataframes automatically

4.

Consider this Spark code snippet with adaptive query execution enabled:

spark.conf.set("spark.sql.adaptive.enabled", "true")

val df1 = spark.range(1000)
val df2 = spark.range(1000000)

val joined = df1.join(df2, df1("id") === df2("id"))
joined.show()

The job runs very slowly. What is the likely cause?

medium

A. Adaptive query execution is disabled by default

B. Adaptive query execution tries to broadcast df2, which is too large

C. The join condition is invalid causing a runtime error

D. Spark automatically caches df2 causing memory overflow

Solution

1. Step 1: Understand adaptive join behavior with large tables

   Adaptive query execution may try to broadcast a table if it thinks it's small enough.

2. Step 2: Analyze table sizes

   df2 has 1,000,000 rows, which is too large to broadcast efficiently, causing slow execution.

3. Final Answer:

   Adaptive query execution tries to broadcast df2, which is too large -> Option B

4. Quick Check:

   Broadcasting large tables causes slow jobs [OK]

Hint: Large table broadcast causes slow join [OK]

Common Mistakes:

• Assuming adaptive is disabled by default
• Thinking join condition is invalid
• Believing Spark caches large tables automatically

5.

You have a Spark job joining three datasets of unknown sizes. How can adaptive query execution help optimize this multi-join query?

hard

A. It forces all joins to be shuffle joins regardless of size

B. It disables all joins and runs map-only jobs

C. It dynamically chooses broadcast or shuffle joins for each join based on runtime data size

D. It requires manual hints to optimize each join

Solution

1. Step 1: Understand adaptive query execution with multiple joins

   Adaptive query execution evaluates data sizes during runtime for each join.

2. Step 2: Explain optimization choice

   It chooses broadcast joins for small tables and shuffle joins for large tables automatically.

3. Step 3: Apply to multi-join scenario

   For three datasets, it optimizes each join individually based on actual data size.

4. Final Answer:

   It dynamically chooses broadcast or shuffle joins for each join based on runtime data size -> Option C

5. Quick Check:

   Adaptive = dynamic join strategy per join [OK]

Hint: Adaptive picks join type per join at runtime [OK]

Common Mistakes:

• Thinking adaptive disables joins
• Assuming all joins become shuffle joins
• Believing manual hints are always required