You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Kirk True (Jira)" <ji...@apache.org> on 2023/12/19 02:47:00 UTC

[jira] [Updated] (KAFKA-15803) Update last seen epoch during commit

     [ https://issues.apache.org/jira/browse/KAFKA-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirk True updated KAFKA-15803:
------------------------------
    Labels: consumer-threading-refactor kip-848-client-support kip-848-e2e kip-848-preview  (was: kip-848-client-support kip-848-e2e kip-848-preview)

> Update last seen epoch during commit
> ------------------------------------
>
>                 Key: KAFKA-15803
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15803
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, consumer
>            Reporter: Philip Nee
>            Assignee: Lucas Brutschy
>            Priority: Major
>              Labels: consumer-threading-refactor, kip-848-client-support, kip-848-e2e, kip-848-preview
>
> At the time we implemented commitAsync in the prototypeAsyncConsumer, metadata was not there. The ask here is to investigate if we need to add the following function to the commit code:
>  
> private void updateLastSeenEpochIfNewer(TopicPartition topicPartition, OffsetAndMetadata offsetAndMetadata) {
> if (offsetAndMetadata != null)
> offsetAndMetadata.leaderEpoch().ifPresent(epoch -> metadata.updateLastSeenEpochIfNewer(topicPartition, epoch));
> }



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