[
https://issues.apache.org/jira/browse/KAFKA-8825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950205#comment-16950205
]
Matthias J. Sax commented on KAFKA-8825:
----------------------------------------
I am not sure about this ticket. Why can't people use police "none" and use
`offsetsForTime()` and `seek()` API? Why can't the described uses cases from
above not apply this pattern?
If course, we could also add this as a "reset policy" but it would just be
syntactic sugar for what is already possible. Do we believe this pattern is
common enough to extend the reset policy (what allows users to write less code)?
For KAFKA-8766 that targets Streams API, it's a little different at users don't
have access to the internal Consumer and thus cannot really use `none` policy
and can also not `seek()` manually.
> Add option to reset consumer offset by relative time
> ----------------------------------------------------
>
> Key: KAFKA-8825
> URL: https://issues.apache.org/jira/browse/KAFKA-8825
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jason Gustafson
> Assignee: Dongjin Lee
> Priority: Major
> Labels: needs-kip
>
> When the consumer first initializes its position or when it encounters an
> offset out of range error, we have two automatic reset policies: earliest and
> latest. With longer retention times, the earliest reset option is often too
> expensive and the latest reset requires more time to build recent context.
> Users can also set an auto reset policy of "none" and handle it themselves,
> but it may be useful to have a configurable option between earliest and
> latest. So a user can reset to one day ago or one hour ago for example. Would
> this be useful?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
