Kafka Streams runner: read a source's splits in parallel

Open
#39,626 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java, kafka

Research direction

Start with ReadTranslator, where split(1, options) currently requires exactly one split, and read the topic-based shuffle work tracked in #18479. The change is done when bounded and unbounded sources can use multiple splits with separate readers and watermarks, distributed across Kafka Streams instances.

Written by the indexing model from the issue text.

Description

Summary

The Kafka Streams runner splits a source into exactly one part and reads it with a single reader, so a source that could be read in parallel is not.

ReadTranslator calls split(1, options) and requires exactly one split back. A source returning more is rejected at translation rather than having the extra splits silently dropped, since that would be data loss, but the effect is that such a source cannot be read at all.

Reading several splits means giving each one its own reader and its own watermark, and distributing them across instances, which belongs with the topic-based shuffle work. Bounded and unbounded sources are both affected.

Part of #18479.

Dominant language
Java
Stars
8.7k
Forks
4.8k
Avg merge
2d 9h
Merged PRs (30d)
368

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/beam

All issues in apache/beam

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.