**Salting**: Add random suffix to skewed keys. key → key_1, key_2, ... key_N. Distributes load across partitions.
**When**: One/few keys dominate (e.g., null, default, popular tenant). Causes stragglers.
**Steps**: Salt key → shuffle (now distributed) → aggregate/join → merge salted groups.
**Why**: Eliminates straggler; job finishes. Without salt, one task runs 10x longer.
**Trade-offs**: Extra shuffle and merge. Salt cardinality = tune....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like American Express. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.