Punctuators for time-based triggers in Kafka - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to schedule a punctuator that triggers every 1000 milliseconds.

Kafka

context.schedule([1], PunctuationType.WALL_CLOCK_TIME, callback);

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

A100

B10000

C1000

D5000

Attempts:

3 left

💡 Hint

Common Mistakes

Using 10000 will trigger every 10 seconds, which is too long for this task.

Using 100 or 5000 will trigger too fast or too slow compared to 1 second.

The schedule method requires the interval in milliseconds. Using 1000 sets the trigger to every 1 second.

2fill in blank

medium

Complete the code to use the correct PunctuationType for wall-clock time triggers.

Kafka

context.schedule(1000, [1], callback);

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

AWALL_CLOCK_TIME

BSTREAM_TIME

CPROCESSING_TIME

DEVENT_TIME

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing STREAM_TIME triggers based on stream progress, not real time.

PROCESSING_TIME is not a valid PunctuationType in Kafka Streams.

WALL_CLOCK_TIME is used to trigger punctuators based on real-world clock time.

3fill in blank

hard

Fix the error in the code to correctly schedule a punctuator every 5 seconds.

Kafka

context.schedule([1], PunctuationType.WALL_CLOCK_TIME, callback);

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

A500

B10000

C50

D5000

Attempts:

3 left

💡 Hint

Common Mistakes

Using 500 triggers every 0.5 seconds, which is too frequent.

Using 10000 triggers every 10 seconds, which is too slow.

The interval must be in milliseconds. 5000 milliseconds equals 5 seconds.

4fill in blank

hard

Fill both blanks to schedule a punctuator every 2 seconds using the correct PunctuationType.

Kafka

context.schedule([1], [2], callback);

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

A2000

BSTREAM_TIME

CWALL_CLOCK_TIME

DPROCESSING_TIME

Attempts:

3 left

💡 Hint

Common Mistakes

Using STREAM_TIME triggers based on stream progress, not real time.

Using 2000 with wrong PunctuationType will not trigger as expected.

2000 milliseconds equals 2 seconds, and WALL_CLOCK_TIME triggers based on real time.

5fill in blank

hard

Fill all three blanks to schedule a punctuator every 3 seconds that prints 'Tick' each time.

Kafka

context.schedule([1], [2], timestamp -> {
    System.out.println([3]);
});

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

A3000

BWALL_CLOCK_TIME

C"Tick"

D"Tock"

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong interval or PunctuationType.

Printing the wrong string like "Tock" instead of "Tick".

3000 milliseconds is 3 seconds, WALL_CLOCK_TIME triggers by real time, and printing "Tick" matches the requirement.

Practice

1. What is the main purpose of a punctuator in Kafka Streams?

easy

A. To run code at regular time intervals inside a stream processing application

B. To send messages to Kafka topics

C. To create new Kafka topics automatically

D. To configure Kafka broker settings

Solution

1. Step 1: Understand what punctuators do

   Punctuators are designed to run code periodically during stream processing.

2. Step 2: Identify the correct purpose

   They are not for sending messages or configuring brokers but for timed callbacks.

3. Final Answer:

   To run code at regular time intervals inside a stream processing application -> Option A

4. Quick Check:

   Punctuator purpose = run code regularly [OK]

Hint: Punctuators trigger code on time intervals, not message sending [OK]

Common Mistakes:

• Confusing punctuators with message producers
• Thinking punctuators create topics
• Assuming punctuators configure Kafka brokers

2. Which of the following is the correct way to schedule a punctuator in Kafka Streams?

easy

A. context.schedule(Duration.ofSeconds(10), PunctuationType.WALL_CLOCK_TIME, callback)

B. context.schedule(10, TimeUnit.SECONDS, callback)

C. context.setTimer(10, callback)

D. context.runEvery(10, callback)

Solution

1. Step 1: Recall the correct method signature

   The Kafka Streams API uses context.schedule() with Duration, PunctuationType, and callback.

2. Step 2: Match the correct syntax

   context.schedule(Duration.ofSeconds(10), PunctuationType.WALL_CLOCK_TIME, callback) matches the correct method call with Duration and PunctuationType.

3. Final Answer:

   context.schedule(Duration.ofSeconds(10), PunctuationType.WALL_CLOCK_TIME, callback) -> Option A

4. Quick Check:

   Correct schedule syntax = context.schedule(Duration.ofSeconds(10), PunctuationType.WALL_CLOCK_TIME, callback) [OK]

Hint: Use context.schedule with Duration and PunctuationType [OK]

Common Mistakes:

• Using incorrect method names like setTimer or runEvery
• Passing integers instead of Duration objects
• Omitting PunctuationType argument

3. Given the following code snippet in a Kafka Streams processor:

context.schedule(Duration.ofMinutes(1), PunctuationType.STREAM_TIME, timestamp -> {
    System.out.println("Punctuator triggered at " + timestamp);
});

What will be printed when the punctuator triggers?

medium

A. Punctuator triggered at current system time in milliseconds

B. Punctuator triggered at the stream time (event time) in milliseconds

C. Punctuator triggered at a fixed string 'timestamp'

D. No output because punctuator is not scheduled correctly

Solution

1. Step 1: Identify the PunctuationType used

   The code uses PunctuationType.STREAM_TIME, which triggers based on event time in the stream.

2. Step 2: Understand the timestamp parameter

   The timestamp passed is the stream time in milliseconds, not system time.

3. Final Answer:

   Punctuator triggered at the stream time (event time) in milliseconds -> Option B

4. Quick Check:

   PunctuationType.STREAM_TIME = stream event time [OK]

Hint: STREAM_TIME triggers use event time, not system clock [OK]

Common Mistakes:

• Confusing STREAM_TIME with WALL_CLOCK_TIME
• Expecting system time instead of stream time
• Assuming no output due to scheduling

4. Identify the error in this Kafka Streams punctuator scheduling code:

context.schedule(5000, PunctuationType.WALL_CLOCK_TIME, timestamp -> {
    System.out.println("Triggered");
});

medium

A. context.schedule cannot be called inside a processor

B. PunctuationType should be STREAM_TIME, not WALL_CLOCK_TIME

C. Callback function must return a value

D. Duration object is missing; integer milliseconds used instead

Solution

1. Step 1: Check the schedule method parameters

   The schedule method expects a Duration object, not an integer.

2. Step 2: Identify the incorrect argument type

   Passing 5000 as int instead of Duration.ofMillis(5000) causes a syntax error.

3. Final Answer:

   Duration object is missing; integer milliseconds used instead -> Option D

4. Quick Check:

   Use Duration, not int, for schedule interval [OK]

Hint: Always use Duration.ofMillis or similar, not raw integers [OK]

Common Mistakes:

• Passing raw integers instead of Duration
• Confusing PunctuationType values
• Thinking callback must return a value

5. You want to emit aggregated results every 30 seconds using a punctuator in Kafka Streams. Which of the following code snippets correctly schedules this punctuator and ensures it triggers based on wall-clock time?

hard

A. context.schedule(30, PunctuationType.WALL_CLOCK_TIME, timestamp -> emitResults())

B. context.schedule(Duration.ofSeconds(30), PunctuationType.STREAM_TIME, timestamp -> emitResults())

C. context.schedule(Duration.ofSeconds(30), PunctuationType.WALL_CLOCK_TIME, timestamp -> emitResults())

D. context.schedule(Duration.ofMinutes(1), PunctuationType.WALL_CLOCK_TIME, timestamp -> emitResults())

Solution

1. Step 1: Determine the correct interval and time type

   The requirement is every 30 seconds and based on wall-clock time.

2. Step 2: Match the correct schedule call

   context.schedule(Duration.ofSeconds(30), PunctuationType.WALL_CLOCK_TIME, timestamp -> emitResults()) uses Duration.ofSeconds(30) and PunctuationType.WALL_CLOCK_TIME, which is correct.

3. Step 3: Check other options for errors

   context.schedule(Duration.ofSeconds(30), PunctuationType.STREAM_TIME, timestamp -> emitResults()) uses STREAM_TIME, not wall-clock; C uses int instead of Duration; D uses 1 minute instead of 30 seconds.

4. Final Answer:

   context.schedule(Duration.ofSeconds(30), PunctuationType.WALL_CLOCK_TIME, timestamp -> emitResults()) -> Option C

5. Quick Check:

   Wall-clock 30s interval = context.schedule(Duration.ofSeconds(30), PunctuationType.WALL_CLOCK_TIME, timestamp -> emitResults()) [OK]

Hint: Use Duration.ofSeconds(30) with WALL_CLOCK_TIME for 30-second triggers [OK]

Common Mistakes:

• Using STREAM_TIME instead of WALL_CLOCK_TIME
• Passing raw integers instead of Duration
• Setting wrong time interval