Self joins in Apache Spark - Step-by-Step Execution

Concept Flow - Self joins

Start with one DataFrame

↓

Create alias for DataFrame as A

↓

Create alias for DataFrame as B

↓

Join A and B on a condition

↓

Result: Rows matched with themselves or related rows

↓

Output DataFrame

Self join means joining a DataFrame with itself using aliases to compare rows within the same data.

Execution Sample

Apache Spark

from pyspark.sql import SparkSession
spark = SparkSession.builder.getOrCreate()
df = spark.createDataFrame([(1, 'A', 10), (2, 'B', 10), (3, 'C', 20)], ['id', 'name', 'group'])
df_alias1 = df.alias('a')
df_alias2 = df.alias('b')
joined = df_alias1.join(df_alias2, df_alias1.group == df_alias2.group).select('a.id', 'a.name', 'b.id', 'b.name')
joined.show()

This code creates a DataFrame and joins it with itself on the 'group' column to find rows sharing the same group.

Execution Table

Step	Action	DataFrame Alias	Condition	Output Rows
1	Create DataFrame	df	N/A	[(1, 'A', 10), (2, 'B', 10), (3, 'C', 20)]
2	Create alias	a	N/A	Same as df
3	Create alias	b	N/A	Same as df
4	Join a and b on a.group == b.group	a, b	a.group == b.group	[(1, 'A', 1, 'A'), (1, 'A', 2, 'B'), (2, 'B', 1, 'A'), (2, 'B', 2, 'B'), (3, 'C', 3, 'C')]
5	Select columns a.id, a.name, b.id, b.name	a, b	N/A	[(1, 'A', 1, 'A'), (1, 'A', 2, 'B'), (2, 'B', 1, 'A'), (2, 'B', 2, 'B'), (3, 'C', 3, 'C')]
6	Show output	N/A	N/A	Displayed rows as above
7	Exit	N/A	No more steps	Execution complete

💡 All matching rows on group column are joined; no more steps.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
df	Empty	[(1, 'A', 10), (2, 'B', 10), (3, 'C', 20)]	Same	Same	Same	Same
df_alias1 (a)	N/A	[(1, 'A', 10), (2, 'B', 10), (3, 'C', 20)]	Same	Same	Same	Same
df_alias2 (b)	N/A	N/A	[(1, 'A', 10), (2, 'B', 10), (3, 'C', 20)]	Same	Same	Same
joined	N/A	N/A	N/A	[(1, 'A', 1, 'A'), (1, 'A', 2, 'B'), (2, 'B', 1, 'A'), (2, 'B', 2, 'B'), (3, 'C', 3, 'C')]	Same	Same

Key Moments - 3 Insights

Why do we need to create aliases for the same DataFrame before joining?

Because joining a DataFrame with itself requires distinguishing the two instances; aliases 'a' and 'b' let Spark know which side of the join each column comes from, as shown in execution_table step 2 and 3.

Why do some rows join with themselves in the output?

Because the join condition matches rows with the same group, including the row itself. For example, row with id 1 joins with itself at step 4 in execution_table.

What happens if we join without a condition?

It would produce a Cartesian product (all combinations), which is usually very large and not useful. The condition 'a.group == b.group' limits the join to meaningful pairs, as in step 4.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, how many rows does the join produce?

A 3

B 5

C 6

D 4

💡 Hint

Check the 'Output Rows' column at step 4 in execution_table.

According to variable_tracker, what is the value of 'joined' after step 5?

A Joined rows with columns a.id, a.name, b.id, b.name

B Empty DataFrame

C Same as df

D Only rows where a.id equals b.id

💡 Hint

Look at the 'joined' row under 'After Step 5' in variable_tracker.

If we change the join condition to 'a.id == b.id', how would the output rows change?

A No rows will join

B All rows will join with all others, more rows

C Only rows where the same id matches, fewer rows

D Output will be the same as original

💡 Hint

Think about how the join condition filters rows in execution_table step 4.

Concept Snapshot

Self joins let you join a DataFrame with itself using aliases.
Use .alias() to create distinct references.
Join on a condition comparing columns from each alias.
Useful to find related rows within the same data.
Remember to select columns carefully to avoid confusion.

Full Transcript

Self joins in Apache Spark mean joining a DataFrame with itself. We start by creating a DataFrame with data. Then we create two aliases for this DataFrame, named 'a' and 'b'. We join these aliases on a condition, for example, where the 'group' column matches. This produces rows where each row is paired with others in the same group, including itself. The output shows columns from both aliases. Aliases are necessary to distinguish the two sides of the join. Without a join condition, the result would be a large Cartesian product. This technique helps find relationships within the same dataset.

Practice

1.

What is the main purpose of a self join in Apache Spark?

easy

A. To join a DataFrame with itself to compare rows within the same dataset

B. To join two different DataFrames based on a common key

C. To merge two DataFrames vertically by stacking rows

D. To filter rows based on a condition

Solution

1. Step 1: Understand the concept of self join

   A self join means joining a DataFrame to itself to compare or relate rows within the same dataset.

2. Step 2: Differentiate from other joins

   Other joins combine different DataFrames or filter rows, but self join specifically uses the same DataFrame twice.

3. Final Answer:

   To join a DataFrame with itself to compare rows within the same dataset -> Option A

4. Quick Check:

   Self join = join DataFrame to itself [OK]

Hint: Self join means joining the same table twice [OK]

Common Mistakes:

• Confusing self join with joining different DataFrames
• Thinking self join stacks rows vertically
• Assuming self join is just filtering rows

2.

Which of the following is the correct way to create aliases for a self join in Spark using DataFrame API?

df1 = df.alias('a')
df2 = df.alias('b')
joined = df1.join(df2, ...)

easy

A. df1 = df.alias('a'); df2 = df.alias('b'); joined = df1.join(df2, 'id')

B. df1 = df; df2 = df; joined = df1.join(df2, 'id')

C. df1 = df.as('a'); df2 = df.as('b'); joined = df1.join(df2, 'id')

D. df1 = df.copy(); df2 = df.copy(); joined = df1.join(df2, 'id')

Solution

1. Step 1: Use alias() method for self join

   In Spark, to join a DataFrame to itself, you create aliases using alias() to distinguish the two references.

2. Step 2: Check the syntax correctness

   df1 = df.alias('a'); df2 = df.alias('b'); joined = df1.join(df2, 'id') uses alias() correctly and joins on a column 'id'. df1 = df.as('a'); df2 = df.as('b'); joined = df1.join(df2, 'id') uses as() which is not a valid DataFrame method in Spark.

3. Final Answer:

   df1 = df.alias('a'); df2 = df.alias('b'); joined = df1.join(df2, 'id') -> Option A

4. Quick Check:

   Use alias() for self join [OK]

Hint: Use alias() to rename DataFrame before self join [OK]

Common Mistakes:

• Using as() instead of alias()
• Not creating aliases and causing ambiguous columns
• Copying DataFrame instead of aliasing

3.

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

from pyspark.sql import SparkSession
spark = SparkSession.builder.getOrCreate()
data = [(1, 'A'), (2, 'B'), (3, 'A')]
df = spark.createDataFrame(data, ['id', 'group'])
df1 = df.alias('df1')
df2 = df.alias('df2')
joined = df1.join(df2, (df1.group == df2.group) & (df1.id != df2.id))
print(joined.count())

medium

A. 2

B. 4

C. 3

D. 6

Solution

1. Step 1: Understand the data and join condition

   Data has 3 rows: (1, 'A'), (2, 'B'), (3, 'A'). The join matches rows with the same group but different ids.

2. Step 2: Count matching pairs

   Group 'A' has ids 1 and 3, so pairs are (1,3) and (3,1) = 2 matches. Group 'B' has only one id, so no match. Total matches = 2 rows. However, since the join is a cross join on the condition, each pair appears twice (once as (1,3) and once as (3,1)), so total count is 4.

3. Final Answer:

   4 -> Option B

4. Quick Check:

   Count matching pairs with condition = 4 [OK]

Hint: Count pairs with same group but different ids [OK]

Common Mistakes:

• Counting only one direction of pairs
• Including rows where id equals
• Ignoring symmetric pairs

4.

Identify the error in this Spark self join code snippet:

df1 = df.alias('a')
df2 = df.alias('b')
joined = df1.join(df2, df1.id == df2.id)
joined.show()

What is the problem?

medium

A. Syntax error in join condition

B. Missing alias() method for DataFrame

C. The join condition causes each row to join with itself, no filtering

D. DataFrame df is not defined

Solution

1. Step 1: Analyze the join condition

   The join condition is df1.id == df2.id, which matches rows with the same id, including the same row joined to itself.

2. Step 2: Identify missing filter to exclude self matches

   There is no condition to exclude rows where the two aliases refer to the same row, so the join includes self matches.

3. Final Answer:

   The join condition causes each row to join with itself, no filtering -> Option C

4. Quick Check:

   Join condition includes self matches [OK]

Hint: Add filter to exclude self matches in self join [OK]

Common Mistakes:

• Not excluding rows where both aliases are same
• Assuming alias() is missing
• Confusing syntax error with logic error

5.

You have a DataFrame df with columns employee_id, manager_id, and department. You want to find pairs of employees who work in the same department and share the same manager but are different employees. Which self join condition is correct?

hard

A. df1.employee_id == df2.employee_id AND df1.manager_id == df2.manager_id

B. df1.employee_id == df2.manager_id AND df1.department == df2.department

C. df1.manager_id != df2.manager_id AND df1.department == df2.department

D. df1.department == df2.department AND df1.manager_id == df2.manager_id AND df1.employee_id != df2.employee_id

Solution

1. Step 1: Understand the requirement

   We want pairs of employees in the same department, with the same manager, but different employee IDs.

2. Step 2: Translate to join condition

   The join condition must check equality of department and manager_id, and inequality of employee_id to avoid self pairs.

3. Final Answer:

   df1.department == df2.department AND df1.manager_id == df2.manager_id AND df1.employee_id != df2.employee_id -> Option D

4. Quick Check:

   Same department & manager, different employees [OK]

Hint: Match same manager and department, exclude same employee [OK]

Common Mistakes:

• Matching employee_id to manager_id incorrectly
• Not excluding same employee pairs
• Checking for different managers instead of same