Question 530
A stateful streaming aggregation retains watermark-free state indefinitely as events arrive every second. The stream is managed with a persistent `writeStream` query and checkpoints. Which explanation most accurately describes the failure mode?
Explanation
Correct Answer
Without event-time limits state can grow without bound for historical keys. This is the most directly relevant technical explanation because without event-time limits state can grow without bound for historical keys. A concrete acceptance check is: State metrics stabilize under long test streams while allowed late records remain included. To reduce recurrence: Monitor late-event discard and state-store size.
Incorrect Answers
Type 2 versioning on every changed attribute creates unnecessary historical rows. Here the important technical distinction is that without event-time limits state can grow without bound for historical keys.
Without dependency edges, jobs can execute eligible tasks concurrently. The reported failure instead depends on this fact: without event-time limits state can grow without bound for historical keys.
Unbounded event-time join state retains data awaiting hypothetical future matches. That consideration does not remove the current constraint: without event-time limits state can grow without bound for historical keys.