[ 
https://issues.apache.org/jira/browse/KAFKA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903916#comment-17903916
 ] 

Peter Lee commented on KAFKA-18014:
-----------------------------------

Hi [~omkreddy], PR is ready, PTAL. Thanks!

> Add duration based offset reset option for ShareConsumer
> --------------------------------------------------------
>
>                 Key: KAFKA-18014
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18014
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Manikumar
>            Assignee: Peter Lee
>            Priority: Major
>             Fix For: 4.1.0
>
>
> Kafka consumer supports auto.offset.reset config option, which is used when 
> there is no initial offset in Kafka (or) if the current offset does not exist 
> any more on the server. This config currently supports earliest/latest/none 
> options. Currently consumer resets might force applications to reprocess 
> large amounts of data from earlier offsets. With infinite storage, its 
> beneficial to have a duration based offset reset strategy. This will allow 
> applications to consume/initialise from a fixed duration when there is no 
> initial offset in Kafka.
> As part of 
> [KIP-932|https://cwiki.apache.org/confluence/display/KAFKA/KIP-932%3A+Queues+for+Kafka],
>  we are adding support for share consumer groups. Share consumer groups 
> supports dynamic group configuration property share.auto.offset.reset. This 
> is used to set the initial Share-Partition Start Offset (SPSO) based on the 
> share.auto.offset.reset configuration. Currently share.auto.offset.reset 
> supports earliest and latest options to automatically reset the offset
> Similar to the Kafka Consumer, we will add support for by_duration: config 
> value for {{{}share.auto.offset.reset{}}}.
> {quote}from 
> [KIP-1106|https://cwiki.apache.org/confluence/display/KAFKA/KIP-1106%3A+Add+duration+based+offset+reset+option+for+consumer+clients]
> {quote}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to