Schema definition and inference in Apache Spark - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to read a CSV file with automatic schema inference.

Apache Spark

df = spark.read.option("header", "true").option("inferSchema", [1]).csv("data.csv")

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

A"true"

BTrue

CFalse

D"false"

Attempts:

3 left

💡 Hint

Common Mistakes

Using boolean True instead of string "true" for option value.

Setting inferSchema to "false" disables schema detection.

Setting option 'inferSchema' to 'true' tells Spark to automatically detect the data types of columns.

2fill in blank

medium

Complete the code to define a schema with a string field 'name' and integer field 'age'.

Apache Spark

from pyspark.sql.types import StructType, StructField, [1], IntegerType
schema = StructType([
    StructField("name", StringType(), True),
    StructField("age", IntegerType(), True)
])

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

AFloatType

BStringType

CBooleanType

DDateType

Attempts:

3 left

💡 Hint

Common Mistakes

Using FloatType or BooleanType instead of StringType for 'name'.

Forgetting to import StringType.

StringType is used to define a string field in the schema.

3fill in blank

hard

Fix the error in the code to apply the schema when reading a JSON file.

Apache Spark

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

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

Aschema

BSchema

Cstruct

DStructType

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the class name StructType instead of the schema variable.

Using incorrect capitalization like 'Schema'.

The variable 'schema' holds the schema object and should be passed to the schema() method.

4fill in blank

hard

Fill both blanks to create a schema with a non-nullable integer field 'id' and a nullable string field 'email'.

Apache Spark

schema = StructType([
    StructField("id", [1](), [2]),
    StructField("email", StringType(), True)
])

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

AIntegerType

BFalse

CTrue

DStringType

Attempts:

3 left

💡 Hint

Common Mistakes

Setting nullable to True for 'id' when it should be False.

Using StringType instead of IntegerType for 'id'.

The 'id' field is an IntegerType and is not nullable, so nullable is set to False.

5fill in blank

hard

Fill all three blanks to create a DataFrame with a schema and show its schema.

Apache Spark

from pyspark.sql import SparkSession
spark = SparkSession.builder.appName("TestApp").getOrCreate()
schema = StructType([
    StructField("name", [1](), True),
    StructField("age", [2](), True)
])
data = [("Alice", 30), ("Bob", 25)]
df = spark.createDataFrame(data, schema=[3])
df.printSchema()

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

AStringType

BIntegerType

Cschema

DStructType

Attempts:

3 left

💡 Hint

Common Mistakes

Passing StructType class instead of schema variable.

Mixing up data types for fields.

Use StringType for 'name', IntegerType for 'age', and pass the schema variable to createDataFrame.

Practice

1. What is the main purpose of defining a schema in Apache Spark?

easy

A. To speed up the Spark installation process

B. To store data permanently on disk

C. To create visualizations automatically

D. To tell Spark the structure and data types of the data

Solution

1. Step 1: Understand what a schema represents

   A schema defines the structure and data types of columns in a dataset.

2. Step 2: Identify the role of schema in Spark

   It helps Spark know how to read and process the data safely and clearly.

3. Final Answer:

   To tell Spark the structure and data types of the data -> Option D

4. Quick Check:

   Schemas = Data structure info [OK]

Hint: Schemas describe data layout and types [OK]

Common Mistakes:

• Thinking schema speeds up installation
• Confusing schema with visualization
• Believing schema stores data permanently

2. Which of the following is the correct way to define a schema manually in Spark using StructType?

easy

A. schema = StructType([StructField('name', StringType(), True), StructField('age', IntegerType(), True)])

B. schema = Struct('name' StringType, 'age' IntegerType)

C. schema = Schema('name': 'string', 'age': 'int')

D. schema = StructType('name', 'age')

Solution

1. Step 1: Recall the syntax for manual schema definition

   In Spark, schemas are defined using StructType with a list of StructField objects.

2. Step 2: Match the correct syntax

   schema = StructType([StructField('name', StringType(), True), StructField('age', IntegerType(), True)]) correctly uses StructType and StructField with data types and nullable flags.

3. Final Answer:

   schema = StructType([StructField('name', StringType(), True), StructField('age', IntegerType(), True)]) -> Option A

4. Quick Check:

   StructType + StructField list = correct schema [OK]

Hint: Use StructType with list of StructField for schemas [OK]

Common Mistakes:

• Omitting parentheses in StructField
• Using wrong class names like Schema or Struct
• Not passing nullable argument

3. Given the following code, what will be the schema of the DataFrame?

from pyspark.sql import SparkSession
from pyspark.sql.types import *
spark = SparkSession.builder.getOrCreate()
data = [('Alice', 30), ('Bob', 25)]
schema = StructType([StructField('name', StringType(), True), StructField('age', IntegerType(), True)])
df = spark.createDataFrame(data, schema)
df.printSchema()

medium

A. root
|-- name: string (nullable = false)
|-- age: integer (nullable = false)

B. root
|-- name: integer (nullable = true)
|-- age: string (nullable = true)

C. root
|-- name: string (nullable = true)
|-- age: integer (nullable = true)

D. root
|-- name: string (nullable = true)
|-- age: string (nullable = true)

Solution

1. Step 1: Analyze the schema definition

   The schema defines 'name' as StringType and 'age' as IntegerType, both nullable True.

2. Step 2: Understand printSchema output

   printSchema shows the root with fields and their types and nullable status.

3. Final Answer:

   root |-- name: string (nullable = true) |-- age: integer (nullable = true) -> Option C

4. Quick Check:

   Schema matches defined types and nullable flags [OK]

Hint: Check schema field types and nullable flags carefully [OK]

Common Mistakes:

• Mixing up data types for fields
• Assuming nullable is False by default
• Confusing printSchema format

4. What is wrong with this schema definition code?

from pyspark.sql.types import StructType, StructField, StringType, IntegerType
schema = StructType([
  StructField('name', StringType),
  StructField('age', IntegerType, True)
])

medium

A. Nullable argument must be False

B. Missing parentheses after StringType and IntegerType

C. StructType should not use a list

D. StructField names should be integers

Solution

1. Step 1: Check usage of data types in StructField

   Data types like StringType and IntegerType must be called with parentheses to create instances.

2. Step 2: Identify the error in the code

   Here, StringType and IntegerType are used without parentheses, causing an error.

3. Final Answer:

   Missing parentheses after StringType and IntegerType -> Option B

4. Quick Check:

   Data types need () to instantiate [OK]

Hint: Always add () after data type classes [OK]

Common Mistakes:

• Forgetting parentheses on data types
• Using wrong types for field names
• Misunderstanding nullable argument

5. You have a JSON file with mixed data types and some missing fields. You want to load it into Spark with a schema that allows missing values and infers types automatically. Which approach is best?

hard

A. Load the JSON without schema and let Spark infer schema automatically

B. Define a manual schema with all fields nullable, then load with that schema

C. Define a schema with all fields non-nullable and load the JSON

D. Convert JSON to CSV first, then load without schema

Solution

1. Step 1: Understand schema inference in Spark

   Spark can automatically detect data types and handle missing fields when loading JSON without a manual schema.

2. Step 2: Compare options for handling missing and mixed types

   Letting Spark infer schema is simpler and handles missing values well; manual schema requires careful nullable settings.

3. Final Answer:

   Load the JSON without schema and let Spark infer schema automatically -> Option A

4. Quick Check:

   Schema inference handles mixed and missing data best [OK]

Hint: Use schema inference for mixed and missing JSON data [OK]

Common Mistakes:

• Making all fields non-nullable causing errors
• Manually defining schema without nullable fields
• Converting JSON unnecessarily before loading