Schema evolution and enforcement in Apache Spark - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to read a JSON file with schema enforcement in Spark.

Apache Spark

df = spark.read.schema([1]).json("data.json")

Drag options to blanks, or click blank then click option'

AinferSchema

BuserSchema

CschemaEnforce

DreadSchema

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'inferSchema' which is a boolean option, not a schema object.

Using method names instead of schema objects.

The schema method requires a defined schema object like userSchema to enforce the schema when reading data.

2fill in blank

medium

Complete the code to enable schema evolution when writing a Delta table.

Apache Spark

df.write.format("delta").option("[1]", "true").mode("append").save("/delta/events")

Drag options to blanks, or click blank then click option'

AoverwriteSchema

BevolveSchema

CmergeSchema

DschemaEvolution

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'overwriteSchema' which is for overwriting the schema, not evolving.

Using made-up option names like 'evolveSchema' or 'schemaEvolution'.

The option mergeSchema set to true allows schema evolution when appending data to a Delta table.

3fill in blank

hard

Fix the error in the code to enforce schema when reading a Parquet file.

Apache Spark

df = spark.read.[1](userSchema).parquet("data.parquet")

Drag options to blanks, or click blank then click option'

Aschema

BinferSchema

Coption

DwithSchema

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'inferSchema' which is a boolean option, not a method.

Using 'option' or 'withSchema' which do not exist.

The correct method to enforce a schema is schema(), not inferSchema or others.

4fill in blank

hard

Fill both blanks to create a DataFrame with a new column and enforce schema on write.

Apache Spark

df2 = df.withColumn("new_col", [1])
df2.write.format("delta").option("[2]", "true").mode("append").save("/delta/events")

Drag options to blanks, or click blank then click option'

Alit(100)

BmergeSchema

Ccol("existing_col") + 1

DoverwriteSchema

Attempts:

3 left

💡 Hint

Common Mistakes

Using a literal value instead of a column expression for the new column.

Using 'overwriteSchema' which is not for schema evolution.

Use col("existing_col") + 1 to create a new column based on an existing one. Use mergeSchema option to allow schema evolution on write.

5fill in blank

hard

Fill all three blanks to create a schema, read JSON with enforcement, and show the DataFrame.

Apache Spark

from pyspark.sql.types import StructType, StructField, [1], StringType

userSchema = StructType([
    StructField("name", StringType(), True),
    StructField("age", [2], True)
])

df = spark.read.schema(userSchema).json("users.json")
df.[3]()

Drag options to blanks, or click blank then click option'

AIntegerType

Cshow

DprintSchema

Attempts:

3 left

💡 Hint

Common Mistakes

Using StringType for age instead of IntegerType.

Using printSchema() instead of show() to display data.

Use IntegerType to define the age field type. Use show() to display the DataFrame content.

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