Why SQL queries on DataFrames in Apache Spark? - Purpose & Use Cases

The Big Idea

What if you could ask your data questions in plain language and get instant answers?

The Scenario

Imagine you have a huge spreadsheet with thousands of rows and columns. You want to find all customers who bought more than 5 items last month. Doing this by scrolling and filtering manually is like searching for a needle in a haystack.

The Problem

Manually filtering data is slow and tiring. It's easy to make mistakes, like missing some rows or mixing up columns. When data grows bigger, manual work becomes impossible and frustrating.

The Solution

Using SQL queries on DataFrames lets you ask questions about your data quickly and clearly. You write simple commands to filter, group, and sort data. The computer does the hard work fast and without errors.

Before vs After

✗ Before

filtered = []
for row in data:
    if row['items_bought'] > 5:
        filtered.append(row)

✓ After

data.createOrReplaceTempView('sales')
result = spark.sql("SELECT * FROM sales WHERE items_bought > 5")

What It Enables

It makes exploring and analyzing big data easy, fast, and reliable, just like asking a smart assistant.

Real Life Example

A store manager quickly finds top-selling products last month by running a SQL query on sales data stored as a DataFrame, instead of digging through endless spreadsheets.

Key Takeaways

Manual data filtering is slow and error-prone.

SQL queries on DataFrames let you ask clear questions to your data.

This approach is fast, accurate, and works well with big data.

Practice

1. What does the createOrReplaceTempView method do in Apache Spark?

easy

A. It registers a DataFrame as a temporary SQL table for querying.

B. It permanently saves the DataFrame to disk as a table.

C. It converts a SQL query into a DataFrame.

D. It deletes a temporary view from Spark.

Solution

1. Step 1: Understand the purpose of createOrReplaceTempView

   This method registers a DataFrame as a temporary table in Spark's SQL context.

2. Step 2: Recognize its use in SQL queries

   Once registered, you can run SQL queries on the DataFrame using spark.sql().

3. Final Answer:

   It registers a DataFrame as a temporary SQL table for querying. -> Option A

4. Quick Check:

   Temporary view = SQL table for queries [OK]

Hint: Temp view means temporary SQL table for queries [OK]

Common Mistakes:

• Thinking it saves data permanently
• Confusing it with running SQL queries
• Assuming it deletes tables

2. Which of the following is the correct syntax to run a SQL query on a DataFrame registered as a temp view named people?

easy

A. spark.execute("SELECT * FROM people")

B. spark.query("SELECT * FROM people")

C. spark.sql("SELECT * FROM people")

D. spark.runSQL("SELECT * FROM people")

Solution

1. Step 1: Identify the correct method to run SQL queries

   The method to run SQL queries on Spark is spark.sql().

2. Step 2: Check the syntax for querying the temp view

   The query string should be passed inside spark.sql() as shown in spark.sql("SELECT * FROM people").

3. Final Answer:

   spark.sql("SELECT * FROM people") -> Option C

4. Quick Check:

   Use spark.sql() to run SQL queries [OK]

Hint: Use spark.sql() to run SQL queries on temp views [OK]

Common Mistakes:

• Using incorrect method names like spark.query
• Forgetting to use quotes around SQL query
• Confusing method names with other APIs

3. Given the following code, what will be the output of the SQL query?

data = [(1, "Alice", 29), (2, "Bob", 31), (3, "Cathy", 25)]
columns = ["id", "name", "age"]
df = spark.createDataFrame(data, columns)
df.createOrReplaceTempView("people")
result = spark.sql("SELECT name FROM people WHERE age > 28 ORDER BY age DESC")
result.show()

medium

A. [["Bob"], ["Cathy"]]

B. [["Alice"], ["Bob"]]

C. [["Cathy"]]

D. [["Bob"], ["Alice"]]

Solution

1. Step 1: Analyze the data and filter condition

   Rows with age > 28 are Alice (29) and Bob (31).

2. Step 2: Apply ORDER BY age DESC

   Ordering by age descending gives Bob (31) first, then Alice (29).

3. Final Answer:

   [["Bob"], ["Alice"]] -> Option D

4. Quick Check:

   Filter age > 28 and order desc = Bob, Alice [OK]

Hint: Filter then order by age descending to get correct order [OK]

Common Mistakes:

• Mixing ascending and descending order
• Including rows with age <= 28
• Confusing column names in SELECT

4. Identify the error in the following code snippet:

df.createOrReplaceTempView("employees")
result = spark.sql("SELECT * FROM employee WHERE salary > 50000")
result.show()

medium

A. The DataFrame was not created before creating temp view.

B. The temp view name is 'employees' but query uses 'employee'.

C. The SQL query syntax is incorrect.

D. The show() method cannot be used on SQL query results.

Solution

1. Step 1: Check temp view name and SQL query table name

   The temp view is named "employees" but the query uses "employee" (missing 's').

2. Step 2: Understand impact of name mismatch

   This causes a runtime error because the table "employee" does not exist.

3. Final Answer:

   The temp view name is 'employees' but query uses 'employee'. -> Option B

4. Quick Check:

   Temp view and query table names must match exactly [OK]

Hint: Check temp view and query table names match exactly [OK]

Common Mistakes:

• Assuming SQL syntax error instead of name mismatch
• Thinking show() can't be used on results
• Ignoring case sensitivity in table names

5. You have a DataFrame sales with columns product, region, and amount. You want to find the total sales amount per region but only for regions where total sales exceed 1000. Which SQL query on the temp view sales will achieve this?

hard

A. SELECT region, SUM(amount) AS total_sales FROM sales GROUP BY region HAVING total_sales > 1000

B. SELECT region, SUM(amount) AS total_sales FROM sales WHERE total_sales > 1000 GROUP BY region

C. SELECT region, SUM(amount) FROM sales GROUP BY region WHERE SUM(amount) > 1000

D. SELECT region, SUM(amount) AS total_sales FROM sales GROUP BY region WHERE total_sales > 1000

Solution

1. Step 1: Understand filtering on aggregated data

   Filtering on aggregated results requires the HAVING clause, not WHERE.

2. Step 2: Check correct use of HAVING with alias

   Using HAVING total_sales > 1000 after GROUP BY is correct as in SELECT region, SUM(amount) AS total_sales FROM sales GROUP BY region HAVING total_sales > 1000.

3. Final Answer:

   SELECT region, SUM(amount) AS total_sales FROM sales GROUP BY region HAVING total_sales > 1000 -> Option A

4. Quick Check:

   Use HAVING to filter grouped aggregates [OK]

Hint: Use HAVING, not WHERE, to filter grouped results [OK]

Common Mistakes:

• Using WHERE instead of HAVING for aggregates
• Placing WHERE after GROUP BY
• Not aliasing SUM(amount) before HAVING