Join operations (KStream-KStream, KStream-KTable) in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a KStream-KStream join in Kafka Streams?

A KStream-KStream join combines two continuous streams of data based on matching keys within a specified time window, producing a new stream with joined records.

beginner

How does a KStream-KTable join differ from a KStream-KStream join?

A KStream-KTable join combines a stream with a table (a changelog of updates), joining each stream record with the latest table value for the matching key, without a time window.

intermediate

What is the role of the time window in a KStream-KStream join?

The time window defines how far apart in time two records with the same key can be to be joined. Only records arriving within this window are joined.

beginner

Why is a KTable considered a 'table' in Kafka Streams?

Because a KTable represents a changelog stream that models the latest state for each key, like a database table with current values.

intermediate

What happens if a KStream record key does not exist in the KTable during a KStream-KTable join?

The join result will be null or absent for the KTable side, so the output depends on the join type (e.g., left join keeps the stream record with null table value).

In a KStream-KStream join, what determines which records are joined?

A Matching keys within a time window

B Matching keys without time constraints

C All records regardless of keys

D Only records from the first stream

KStream-KStream joins require matching keys and that records arrive within a specified time window to be joined.

What type of join allows a KStream to join with the latest state of a KTable?

A KStream-KStream join

B GlobalKTable join

C KTable-KTable join

D KStream-KTable join

KStream-KTable join combines a stream with the latest state from a table (KTable).

Which join type in Kafka Streams uses a time window?

A KStream-KStream join

B KStream-KTable join

C KTable-KTable join

D None of the above

Only KStream-KStream joins require a time window to match records.

If a KStream record key is missing in the KTable during a left join, what is the output?

A The record is dropped

B The record is joined with null for the KTable value

C An error occurs

D The record is duplicated

In a left join, the stream record is kept with null for the missing table value.

What does a KTable represent in Kafka Streams?

A A stream of events

B A batch of records

C A changelog stream representing the latest state per key

D A static file

A KTable models the latest state for each key as a changelog stream.

Explain how a KStream-KStream join works and why a time window is important.

Think about how two live streams combine their records based on time and keys.

Describe the difference between a KStream-KTable join and a KStream-KStream join.

Consider how a stream joins with a changing table versus another stream.

Practice

1. What is the main difference between a KStream-KStream join and a KStream-KTable join in Kafka Streams?

easy

A. KStream-KStream joins require a time window; KStream-KTable joins do not.

B. KStream-KTable joins require a time window; KStream-KStream joins do not.

C. Both joins require a time window to match records.

D. Neither join requires a time window.

Solution

1. Step 1: Understand KStream-KStream join behavior

   KStream-KStream joins combine records from two streams that occur within a specified time window.

2. Step 2: Understand KStream-KTable join behavior

   KStream-KTable joins enrich stream records with the latest matching table record without needing a time window.

3. Final Answer:

   KStream-KStream joins require a time window; KStream-KTable joins do not. -> Option A

4. Quick Check:

   Time window needed only for KStream-KStream joins [OK]

Hint: Remember: only KStream-KStream joins need time windows [OK]

Common Mistakes:

• Confusing which join requires a time window
• Thinking both joins behave the same
• Assuming KStream-KTable join needs time window

2. Which of the following is the correct syntax to perform a KStream-KTable join in Kafka Streams?

easy

A. ktable.join(kstream, (tableValue, streamValue) -> tableValue + streamValue);

B. kstream.join(ktable, JoinWindows.of(Duration.ofMinutes(5)), (v1, v2) -> v1 + v2);

C. kstream.join(ktable, (streamValue, tableValue) -> streamValue + tableValue);

D. kstream.join(ktable, (v1, v2) -> v1 + v2, JoinWindows.of(Duration.ofMinutes(5)));

Solution

1. Step 1: Identify KStream-KTable join syntax

   KStream-KTable join uses kstream.join(ktable, ValueJoiner) without a time window.

2. Step 2: Check options for correct method signature

   kstream.join(ktable, (streamValue, tableValue) -> streamValue + tableValue); matches the correct syntax: join without window and with a ValueJoiner lambda.

3. Final Answer:

   kstream.join(ktable, (streamValue, tableValue) -> streamValue + tableValue); -> Option C

4. Quick Check:

   KStream-KTable join syntax = kstream.join(ktable, (streamValue, tableValue) -> streamValue + tableValue); [OK]

Hint: KStream-KTable join has no time window parameter [OK]

Common Mistakes:

• Adding JoinWindows to KStream-KTable join
• Reversing stream and table parameters
• Using KTable join method on KStream

3. Given the following Kafka Streams code snippet, what will be the output if the input streams have matching keys within the 5-minute window?

var joinedStream = stream1.join(stream2, (v1, v2) -> v1 + v2, JoinWindows.of(Duration.ofMinutes(5)));
joinedStream.foreach((key, value) -> System.out.println(key + ":" + value));

medium

A. Prints combined values for keys appearing in both streams within 5 minutes

B. Prints combined values for all keys in stream1 regardless of stream2

C. Prints only keys from stream2 with no combination

D. Throws a runtime exception due to missing KTable

Solution

1. Step 1: Understand KStream-KStream join with window

   The join combines records from both streams with matching keys occurring within the 5-minute window.

2. Step 2: Analyze output behavior

   For matching keys within the window, the values are combined using the lambda (v1 + v2) and printed.

3. Final Answer:

   Prints combined values for keys appearing in both streams within 5 minutes -> Option A

4. Quick Check:

   KStream-KStream join outputs combined matching keys [OK]

Hint: KStream-KStream join outputs combined values within window [OK]

Common Mistakes:

• Assuming all keys from stream1 print regardless of stream2
• Confusing KStream-KTable join behavior
• Expecting runtime error without KTable

4. Identify the error in the following Kafka Streams join code:

var joined = stream1.join(stream2, (v1, v2) -> v1 + v2);
joined.print();

medium

A. Incorrect lambda syntax for join function

B. Missing JoinWindows parameter for KStream-KStream join

C. Using print() instead of foreach() causes error

D. stream2 should be a KTable, not a KStream

Solution

1. Step 1: Check join method parameters

   KStream-KStream join requires a JoinWindows parameter to specify the time window for matching events.

2. Step 2: Identify missing parameter

   The code omits the JoinWindows argument, causing a compilation error.

3. Final Answer:

   Missing JoinWindows parameter for KStream-KStream join -> Option B

4. Quick Check:

   KStream-KStream join needs JoinWindows [OK]

Hint: KStream-KStream join always needs JoinWindows [OK]

Common Mistakes:

• Forgetting JoinWindows in KStream-KStream join
• Confusing KStream-KTable join syntax
• Assuming print() is invalid method

5. You want to enrich a stream of user clicks (KStream) with the latest user profile data stored in a KTable. Which join operation should you use and why?

hard

A. Use KStream-KStream join without a window to join clicks and profiles.

B. Use KStream-KStream join with a 10-minute window to combine clicks and profiles.

C. Use KTable-KTable join because both are tables.

D. Use KStream-KTable join to enrich clicks with latest profile data without time window.

Solution

1. Step 1: Identify data types and join needs

   User clicks are a stream (KStream), and user profiles are stored as a table (KTable).

2. Step 2: Choose appropriate join type

   KStream-KTable join enriches stream data with the latest table data for matching keys without needing a time window.

3. Final Answer:

   Use KStream-KTable join to enrich clicks with latest profile data without time window. -> Option D

4. Quick Check:

   KStream-KTable join enriches stream with latest table data [OK]

Hint: Enrich stream with table data using KStream-KTable join [OK]

Common Mistakes:

• Using KStream-KStream join unnecessarily
• Adding time window to KStream-KTable join
• Confusing KTable-KTable join for stream enrichment