

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 4
click for more info
Not enough gems
Cost: 6 gems
1: Data Merging
incomplete
2: Inner and Left Joins
incomplete
3: Outer Joins
incomplete
4: Merging on Different Keys
incomplete
5: Merging on Composite Keys
incomplete
6: Handling Column Name Conflicts
incomplete
7: Understanding Cardinality
incomplete
8: Merge Validation
incomplete
9: Finding Unmatched Records
incomplete
10: Multi-Table Joins
incomplete
11: Concatenating DataFrames
incomplete
12: Standardizing Schemas
incomplete
13: Building an Integration Pipeline
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
Real data almost never lives in one neat table. You might have:
customers.csv with customer infoorders.csv with purchasesproducts.csv with product detailsIf you want customer names, product details, and order history in one place, you need to combine those datasets by matching shared keys. In Pandas you'll usually do that with pd.merge().
We use the term merge in Pandas to refer to this process; it's similar to what SQL calls a JOIN. Different join types answer different kinds of questions.
Production data is often normalized, which means related information is split across multiple tables to avoid duplication. Analysis usually wants the opposite: a wider dataset with the relevant context all in a single place. That's how you answer questions like: