Watermarking for late data in Apache Spark - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is watermarking in Apache Spark Structured Streaming?

Watermarking is a technique to handle late data by specifying a threshold time. It tells Spark to wait for late data up to a certain delay and then drop data older than that to manage state and avoid infinite waiting.

beginner

Why do we need watermarking when processing streaming data?

Because streaming data can arrive late or out of order, watermarking helps Spark decide when to stop waiting for late data and clean up old state, ensuring efficient and timely processing.

intermediate

How do you set a watermark in Spark Structured Streaming code?

You use the method `.withWatermark(eventTimeColumn, delayThreshold)` on a streaming DataFrame, where `eventTimeColumn` is the timestamp column and `delayThreshold` is the max allowed lateness, like '10 minutes'.

beginner

What happens to data that arrives later than the watermark threshold?

Data arriving later than the watermark threshold is considered too late and is dropped from processing to avoid incorrect results and to free resources.

intermediate

Explain the relationship between watermarking and state cleanup in streaming aggregations.

Watermarking defines how long Spark keeps state for aggregations. Once data is older than the watermark, Spark can safely remove its state, preventing memory buildup and improving performance.

What does watermarking in Spark Structured Streaming help manage?

A Data visualization

B Data encryption

C Batch job scheduling

D Late arriving data

Watermarking helps manage late arriving data by setting a threshold for how late data can arrive before being dropped.

Which method is used to set a watermark in Spark Structured Streaming?

A withWatermark()

B setWatermark()

C watermark()

D defineWatermark()

The correct method to set watermark is withWatermark(eventTimeColumn, delayThreshold).

If the watermark delay is set to '5 minutes', what happens to data arriving 6 minutes late?

A It is dropped as too late

B It is processed normally

C It triggers an error

D It is stored for later processing

Data arriving later than the watermark delay is dropped to avoid stale or incorrect results.

Watermarking helps Spark to:

A Keep state forever

B Ignore all late data

C Clean up old state after a delay

D Run batch jobs faster

Watermarking allows Spark to clean up old state after the watermark delay, managing memory efficiently.

Which column is typically used for watermarking in streaming data?

A User ID column

B Event timestamp column

C Partition column

D Random number column

Watermarking uses the event timestamp column to track lateness of data.

Describe how watermarking works in Apache Spark Structured Streaming and why it is important.

Think about how Spark decides when to stop waiting for late data.

Explain the impact of watermarking on streaming aggregation state and resource management.

Consider how watermarking helps Spark manage memory and correctness.

Practice

1. What is the main purpose of watermarking in Apache Spark streaming?

easy

A. To handle late data by setting a threshold time for event processing

B. To speed up the streaming job by skipping data

C. To permanently store all incoming data

D. To convert batch data into streaming data

Solution

1. Step 1: Understand watermarking concept

   Watermarking sets a time limit to wait for late data in streaming.

2. Step 2: Identify purpose in streaming

   It helps to ignore data that arrives too late to keep results timely.

3. Final Answer:

   To handle late data by setting a threshold time for event processing -> Option A

4. Quick Check:

   Watermarking = handle late data [OK]

Hint: Watermarking sets max wait time for late events [OK]

Common Mistakes:

• Thinking watermark speeds up jobs by skipping all data
• Confusing watermark with data storage
• Assuming watermark converts batch to streaming

2. Which of the following is the correct syntax to add a watermark on a streaming DataFrame df with event time column eventTime and delay threshold of 10 minutes?

easy

A. df.withWatermark(eventTime, 10)

B. df.withWatermark("eventTime", "10 minutes")

C. df.watermark("eventTime", 10)

D. df.withWatermark("eventTime", 10)

Solution

1. Step 1: Recall correct method signature

   The method is withWatermark with two string arguments: column name and delay duration.

2. Step 2: Match correct syntax

   df.withWatermark("eventTime", "10 minutes") uses correct method and string format for delay "10 minutes".

3. Final Answer:

   df.withWatermark("eventTime", "10 minutes") -> Option B

4. Quick Check:

   Correct syntax uses strings for both args [OK]

Hint: Use strings for column and delay in withWatermark() [OK]

Common Mistakes:

• Passing column name without quotes
• Using integer instead of string for delay
• Using wrong method name like watermark()

3. Given the following Spark Structured Streaming code snippet, what will be the output schema's watermark column after applying watermark?

val streamingDF = spark.readStream.format("csv")
  .option("header", "true")
  .load("/data/events")

val withWatermarkDF = streamingDF.withWatermark("eventTime", "5 minutes")
withWatermarkDF.printSchema()

medium

A. eventTime: timestamp (nullable = true) with watermark

B. eventTime: string (nullable = true) with watermark

C. eventTime: timestamp (nullable = false) without watermark

D. No watermark added to schema

Solution

1. Step 1: Understand watermark effect on schema

   Watermark adds metadata to the event time column, which must be timestamp type.

2. Step 2: Check expected schema output

   Schema shows eventTime as timestamp with watermark metadata.

3. Final Answer:

   eventTime: timestamp (nullable = true) with watermark -> Option A

4. Quick Check:

   Watermark adds metadata to timestamp column [OK]

Hint: Watermark adds metadata to timestamp event column [OK]

Common Mistakes:

• Assuming eventTime remains string type
• Thinking watermark changes nullability
• Believing watermark does not affect schema

4. Identify the error in the following Spark Structured Streaming code that uses watermarking:

val df = spark.readStream.format("json")
  .load("/stream/data")

val result = df.withWatermark("timestamp", "1 minute")
  .groupBy(window(col("timestamp"), "30 seconds"))
  .count()

medium

A. withWatermark must be called after groupBy

B. Column name "timestamp" should be "eventTime"

C. Window duration cannot be "30 seconds"

D. Watermark delay must be shorter than window duration

Solution

1. Step 1: Check watermark and window durations

   Watermark delay must be shorter than window duration to ensure the query emits results.

2. Step 2: Compare durations in code

   Watermark is 1 minute but window is 30 seconds, watermark delay longer than window duration and causes error.

3. Final Answer:

   Watermark delay must be shorter than window duration -> Option D

4. Quick Check:

   Watermark < window duration [OK]

Hint: Watermark delay must be < window duration [OK]

Common Mistakes:

• Assuming any column name works
• Thinking window duration cannot be "30 seconds"
• Calling withWatermark after groupBy

5. You have a streaming dataset with event times and want to aggregate counts per 10-minute window. Late data can arrive up to 15 minutes late. Which watermark delay should you set to ensure correct results without excessive delay?

hard

A. "25 minutes"

B. "10 minutes"

C. "15 minutes"

D. "5 minutes"

Solution

1. Step 1: Understand watermark delay role

   Watermark delay should cover the maximum expected lateness of data to include late events.

2. Step 2: Match delay to late data arrival

   Since late data can arrive up to 15 minutes late, watermark delay must be at least 15 minutes.

3. Step 3: Avoid setting delay too short or too long

   Setting delay less than 15 minutes risks dropping late data; too long delays output.

4. Final Answer:

   "15 minutes" -> Option C

5. Quick Check:

   Watermark delay = max late arrival [OK]

Hint: Set watermark delay to max expected late arrival [OK]

Common Mistakes:

• Setting delay equal to window size instead of late arrival
• Using shorter delay than late data time
• Using unnecessarily long delay causing latency