Why Window functions in Apache Spark? - Purpose & Use Cases

The Big Idea

What if you could get running totals and rankings instantly without messy manual work?

The Scenario

Imagine you have a huge table of sales data and you want to find the running total of sales for each store by date. Doing this by hand means opening a spreadsheet, sorting data, and adding numbers one by one for each store and date.

The Problem

Manually calculating running totals or rankings is slow and tiring. It's easy to make mistakes when adding or sorting data by hand. Also, if the data changes, you have to redo everything from scratch, which wastes time and causes frustration.

The Solution

Window functions let you calculate running totals, ranks, or moving averages directly in your data queries. They work like a smart helper that looks at a group of rows around each row and performs calculations automatically, saving you from manual work and errors.

Before vs After

✗ Before

for each store:
  sort sales by date
  running_total = 0
  for each sale:
    running_total += sale_amount
    print running_total

✓ After

SELECT store, date, sale_amount,
       SUM(sale_amount) OVER (PARTITION BY store ORDER BY date ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW) AS running_total
FROM sales_table

What It Enables

Window functions make it easy to analyze data trends over time or groups without losing the original data rows, unlocking powerful insights with simple queries.

Real Life Example

A retail manager can quickly see how daily sales accumulate for each store, helping to spot growth trends or slow days without complex manual calculations.

Key Takeaways

Manual calculations for running totals or rankings are slow and error-prone.

Window functions automate these calculations within your data queries.

This saves time, reduces mistakes, and reveals insights easily.

Practice

1. What is the main purpose of window functions in Apache Spark?

easy

A. To perform calculations across rows related to the current row without collapsing the data

B. To group data and reduce the number of rows

C. To filter rows based on a condition

D. To join two datasets together

Solution

1. Step 1: Understand window function behavior

   Window functions calculate values across related rows but keep all original rows intact.

2. Step 2: Compare with grouping

   Grouping reduces rows by aggregation, but window functions add columns without reducing rows.

3. Final Answer:

   To perform calculations across rows related to the current row without collapsing the data -> Option A

4. Quick Check:

   Window functions add calculations without grouping ≠ A [OK]

Hint: Window functions add columns, grouping reduces rows [OK]

Common Mistakes:

• Confusing window functions with groupBy aggregations
• Thinking window functions filter rows
• Assuming window functions join datasets

2. Which of the following is the correct way to define a window specification in PySpark to partition by 'department' and order by 'salary'?

easy

A. Window.groupBy('department').sortBy('salary')

B. Window.sortBy('salary').partitionBy('department')

C. Window.partitionBy('department').orderBy('salary')

D. Window.partition('department').order('salary')

Solution

1. Step 1: Recall PySpark window spec syntax

   The correct methods are partitionBy() and orderBy() chained on Window.

2. Step 2: Check method order and names

   partitionBy comes first, then orderBy; groupBy and sortBy are incorrect here.

3. Final Answer:

   Window.partitionBy('department').orderBy('salary') -> Option C

4. Quick Check:

   Use partitionBy then orderBy methods [OK]

Hint: Use Window.partitionBy().orderBy() exactly [OK]

Common Mistakes:

• Using groupBy instead of partitionBy
• Using sortBy instead of orderBy
• Using incorrect method names like partition or order

3. Given the following PySpark code, what will be the output of the 'rank' column?

from pyspark.sql import SparkSession
from pyspark.sql.window import Window
from pyspark.sql.functions import rank

spark = SparkSession.builder.getOrCreate()
data = [("Alice", "Sales", 5000), ("Bob", "Sales", 4000), ("Charlie", "Sales", 5000)]
df = spark.createDataFrame(data, ["name", "department", "salary"])
windowSpec = Window.partitionBy("department").orderBy("salary")
df = df.withColumn("rank", rank().over(windowSpec))
df.orderBy("salary").show()

medium

A. [ ("Bob", 4000, 1), ("Alice", 5000, 2), ("Charlie", 5000, 2) ]

B. [ ("Bob", 4000, 1), ("Alice", 5000, 3), ("Charlie", 5000, 3) ]

C. [ ("Bob", 4000, 1), ("Alice", 5000, 2), ("Charlie", 5000, 3) ]

D. [ ("Bob", 4000, 1), ("Alice", 5000, 1), ("Charlie", 5000, 1) ]

Solution

1. Step 1: Understand rank() behavior

   Rank assigns the same rank to ties and skips ranks after ties.

2. Step 2: Apply rank over salary ascending

   Bob has salary 4000 ranked 1; Alice and Charlie both have 5000, so both get rank 2.

3. Final Answer:

   [ ("Bob", 4000, 1), ("Alice", 5000, 2), ("Charlie", 5000, 2) ] -> Option A

4. Quick Check:

   rank() ties share rank, next rank skips [OK]

Hint: rank() gives same rank to ties, skips next ranks [OK]

Common Mistakes:

• Confusing rank() with dense_rank()
• Assigning different ranks to tied values
• Not ordering data before applying rank

4. Identify the error in this PySpark code snippet using window functions:

from pyspark.sql.window import Window
from pyspark.sql.functions import row_number

windowSpec = Window.partitionBy('department')
df = df.withColumn('row_num', row_number().over(windowSpec.orderBy('salary')))

medium

A. Missing import for Window functions causes error

B. windowSpec.orderBy('salary') is valid; no error in code

C. row_number() cannot be used with partitionBy

D. windowSpec.orderBy('salary') is invalid; orderBy should be called on Window, not on windowSpec

Solution

1. Step 1: Check windowSpec usage

   windowSpec is a WindowSpec object; calling orderBy on it is valid and returns a new WindowSpec.

2. Step 2: Confirm chaining

   Chaining orderBy on windowSpec is allowed to refine the window specification.

3. Final Answer:

   windowSpec.orderBy('salary') is valid; no error in code -> Option B

4. Quick Check:

   WindowSpec supports chaining orderBy to refine window [OK]

Hint: WindowSpec supports chaining orderBy to refine window [OK]

Common Mistakes:

• Calling orderBy on windowSpec instead of Window
• Assuming row_number can't be used with partitionBy
• Forgetting to import Window or functions

5. You have a sales dataset with columns: 'store', 'date', and 'sales'. You want to add a column showing the 3-day moving average of sales per store ordered by date. Which PySpark window function setup and code will achieve this?

hard

A. Use Window.partitionBy('store').orderBy('date').rowsBetween(0, 2) and avg('sales').over(windowSpec)

B. Use Window.partitionBy('store').orderBy('date').rangeBetween(-2, 0) and avg('sales').over(windowSpec)

C. Use Window.orderBy('date').rowsBetween(-3, 0) and avg('sales').over(windowSpec)

D. Use Window.partitionBy('store').orderBy('date').rowsBetween(-2, 0) and avg('sales').over(windowSpec)

Solution

1. Step 1: Define window for 3-day moving average per store

   Partition by 'store' to separate stores, order by 'date' for time sequence, use rowsBetween(-2, 0) for current and previous 2 rows.

2. Step 2: Apply avg() over this window

   Use avg('sales').over(windowSpec) to compute moving average over the defined window.

3. Final Answer:

   Use Window.partitionBy('store').orderBy('date').rowsBetween(-2, 0) and avg('sales').over(windowSpec) -> Option D

4. Quick Check:

   rowsBetween(-2,0) for 3-day window, partition by store [OK]

Hint: Use rowsBetween(-2,0) for 3-row moving average [OK]

Common Mistakes:

• Using rangeBetween instead of rowsBetween for row count
• Not partitioning by store
• Using wrong rowsBetween range (like 0 to 2)