Schema evolution and enforcement in Apache Spark - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is schema evolution in Apache Spark?

Schema evolution means Spark can handle changes in data structure over time, like adding or removing columns, without breaking the data processing.

beginner

What does schema enforcement mean in Spark?

Schema enforcement means Spark checks that incoming data matches the expected structure exactly, rejecting or fixing data that doesn't fit.

intermediate

How does Spark handle adding a new column during schema evolution?

Spark can add the new column with null values for old data, so the data fits the new schema without errors.

intermediate

What happens if data does not match the enforced schema in Spark?

Spark will throw an error or reject the data, preventing incorrect data from entering the system.

intermediate

Name a Spark feature that helps with schema evolution.

The 'mergeSchema' option in Spark allows automatic merging of schemas when reading data with different structures.

What does schema evolution allow in Apache Spark?

A Encrypting data automatically

B Handling changes in data structure over time

C Rejecting all data that doesn't match schema

D Compressing data files

Schema evolution lets Spark handle changes like new or missing columns without errors.

What is the purpose of schema enforcement?

A To ensure data matches expected structure

B To allow any data format

C To speed up data processing

D To backup data automatically

Schema enforcement checks that data fits the expected schema exactly.

Which Spark option helps merge different schemas automatically?

A autoSchema

B schemaLock

C schemaCheck

D mergeSchema

The 'mergeSchema' option merges schemas when reading data with different structures.

If a new column is added in schema evolution, what does Spark do with old data?

A Fills new column with nulls for old data

B Deletes old data

C Ignores the new column

D Duplicates old data

Spark fills the new column with nulls for old data to keep schema consistent.

What happens if data violates schema enforcement?

A Spark fixes the data automatically

B Spark compresses the data

C Spark throws an error or rejects data

D Spark ignores the schema

Spark rejects or errors out when data does not match the enforced schema.

Explain schema evolution and how Spark manages changes in data structure.

Think about how data changes over time and how Spark adapts.

Describe schema enforcement and its importance in data processing with Spark.

Consider why strict data structure is important.

Practice

1. What does schema evolution in Apache Spark allow you to do?

easy

A. Add or change columns without breaking old data

B. Automatically delete old data files

C. Enforce strict data types on all columns

D. Compress data files for faster reading

Solution

1. Step 1: Understand schema evolution concept

   Schema evolution means you can update the schema by adding or changing columns without losing compatibility with existing data.

2. Step 2: Compare options with definition

   Only Add or change columns without breaking old data correctly describes this ability. Other options describe unrelated features.

3. Final Answer:

   Add or change columns without breaking old data -> Option A

4. Quick Check:

   Schema evolution = Add/change columns safely [OK]

Hint: Schema evolution means changing schema without breaking data [OK]

Common Mistakes:

• Confusing schema evolution with schema enforcement
• Thinking schema evolution deletes old data
• Assuming schema evolution compresses data

2. Which option correctly enables schema merging when reading Parquet files in Spark?

easy

A. spark.read.option("schemaEvolution", "enabled").parquet(path)

B. spark.read.option("enforceSchema", "true").parquet(path)

C. spark.read.option("merge", "false").parquet(path)

D. spark.read.option("mergeSchema", "true").parquet(path)

Solution

1. Step 1: Recall correct option name for schema merging

   The correct option to merge schemas is "mergeSchema" set to "true".

2. Step 2: Verify syntax correctness

   spark.read.option("mergeSchema", "true").parquet(path) uses the exact syntax spark.read.option("mergeSchema", "true").parquet(path), which is valid.

3. Final Answer:

   spark.read.option("mergeSchema", "true").parquet(path) -> Option D

4. Quick Check:

   Use mergeSchema=true to merge schemas [OK]

Hint: Use mergeSchema option set to true for schema merging [OK]

Common Mistakes:

• Using wrong option names like enforceSchema or schemaEvolution
• Setting mergeSchema to false disables merging
• Confusing option names with other Spark settings

3. Given two Parquet files with schemas:
file1: (id INT, name STRING)
file2: (id INT, name STRING, age INT)
What will be the schema of the DataFrame when reading both files with mergeSchema=true?

medium

A. (id INT, name STRING, age INT)

B. (id INT, name STRING)

C. (id INT, age INT)

D. (name STRING, age INT)

Solution

1. Step 1: Understand schema merging behavior

   When mergeSchema=true, Spark combines all columns from all files, including new columns.

2. Step 2: Combine columns from both schemas

   file1 has (id, name), file2 adds (age). Merged schema includes all three columns.

3. Final Answer:

   (id INT, name STRING, age INT) -> Option A

4. Quick Check:

   Merged schema includes all columns from files [OK]

Hint: Merged schema includes all columns from all files [OK]

Common Mistakes:

• Ignoring new columns in second file
• Assuming schema stays as first file only
• Dropping columns not in all files

4. You try to read Parquet files with different schemas but get an error about schema mismatch. What is the likely cause?

medium

A. The files are corrupted

B. You did not set mergeSchema option to true

C. You used the wrong file path

D. Spark does not support schema evolution

Solution

1. Step 1: Identify cause of schema mismatch error

   Schema mismatch errors happen when Spark tries to read files with different schemas without merging enabled.

2. Step 2: Check mergeSchema option usage

   Not setting mergeSchema=true causes Spark to expect identical schemas, leading to errors.

3. Final Answer:

   You did not set mergeSchema option to true -> Option B

4. Quick Check:

   Enable mergeSchema=true to avoid schema mismatch errors [OK]

Hint: Set mergeSchema=true to fix schema mismatch errors [OK]

Common Mistakes:

• Blaming file corruption without checking options
• Assuming Spark cannot evolve schemas
• Ignoring mergeSchema option

5. You have a Delta Lake table with schema (id INT, name STRING). You want to add a new column age INT and keep old data accessible. Which approach correctly applies schema evolution and enforcement?

hard

A. Overwrite the table schema manually without options

B. Delete old data and write new data with new schema

C. Use ALTER TABLE ADD COLUMN age INT and write new data with mergeSchema=true

D. Read old data without options and append new data with new schema

Solution

1. Step 1: Add new column using ALTER TABLE

   ALTER TABLE ADD COLUMN adds the new column to the Delta table schema safely.

2. Step 2: Write new data with mergeSchema=true

   Writing with mergeSchema=true allows Spark to merge new schema with old data without errors.

3. Final Answer:

   Use ALTER TABLE ADD COLUMN age INT and write new data with mergeSchema=true -> Option C

4. Quick Check:

   ALTER TABLE + mergeSchema=true enables safe schema evolution [OK]

Hint: Use ALTER TABLE and mergeSchema=true to evolve Delta schema safely [OK]

Common Mistakes:

• Overwriting schema without mergeSchema causes data loss
• Deleting old data loses history
• Appending without mergeSchema causes errors