KafkaIO bounded source
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
KafkaIO could be a useful source for batch applications as well. It could implement a bounded source. The primary question is how the bounds are specified.
One option : Source specifies a time period (say 9am-10am), and KafkaIO fetches appropriate start and end offsets based on time-index in Kafka. This would suite many batch applications that are launched on a scheduled.
Another option is to always read till the end and commit the offsets to Kafka. Handling failures and multiple runs of a task might be complicated.
Imported from Jira [BEAM-2185](https://issues.apache.org/jira/browse/BEAM-2185). Original Jira may contain additional context.
Reported by: rangadi.
Contributor guide
Research direction
Start by reading the KafkaIO source and the linked BEAM-2185 Jira context; the issue does not name specific files or tests. Compare time-bounded offsets with reading to the end and committing offsets, then define the failure and repeated-run behavior that a bounded source must support before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100