Description
Today we only have one consumer config "offset.auto.reset" to control that behavior, which means all streams are read either from "earliest" or "latest".
However, it would be useful to improve this settings to allow users have finer control over different input stream. For example, with two input streams, one of them always reading from offset 0 upon (re)-starting, and the other reading for log end offset.
This JIRA requires to extend KStreamBuilder API for methods .stream(...) and .table(...) to add a new parameter that indicate the initial offset to be used.
Attachments
Issue Links
- is related to
-
KAFKA-3478 Finer Stream Flow Control
-
- Resolved
-
- relates to
-
KAFKA-4144 Allow per stream/table timestamp extractor
-
- Resolved
-
- links to
