Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Partitioning: Splits by column (e.g., dt, region); pruning skips non-matching partitions. Bucketing: Hashes rows into N files by key; enables co-located joins when both tables bucketed on same key. Why combined: PARTITIONED BY (dt) CLUSTERED BY (user_id) INTO 32 BUCKETS—prune by...
This medium-level SQL question appears frequently in data engineering interviews at companies like Adidas. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (join, partition, spark) will help you answer variations of this question confidently.
Break this problem into components. Identify the core trade-offs involved, then walk the interviewer through your reasoning step by step. Demonstrate awareness of edge cases and production considerations - this is what separates good answers from great ones.
Partitioning: Splits by column (e.g., dt, region); pruning skips non-matching partitions. Bucketing: Hashes rows into N files by key; enables co-located joins when both tables bucketed on same key. Why combined: PARTITIONED BY (dt) CLUSTERED BY (user_id) INTO 32 BUCKETS—prune by date, efficient join on user_id. Trade-offs: Partition cardinality too high (e.g., by hour for years) → small-file problem, metadata overload; too low → coarse pruning. Bucket count: Too many → tiny files, task overhead; too few → skew, large shuffles. Over-partitioning: Hundreds of thousands of partitions stress metastore and listing. Over-bucketing: Files smaller than block size waste I/O. Cost: Small files increase task count, S3 LIST calls; co-location reduces shuffle. Best practice: Partition by high-filter columns; bucket by join keys; target ~128MB–256MB per file.
Red Flag: Partitioning by high-cardinality column (e.g., user_id) without bucketing—explosion of partitions. Pro-Move: Partition by low-cardinality (date, region); bucket by high-cardinality join key; size buckets for 2–4x cluster parallelism.
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.