You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Andrew Schofield (Jira)" <ji...@apache.org> on 2025/07/27 21:39:00 UTC
[jira] [Resolved] (KAFKA-19471) Enable acknowledgement for a record which could not be deserialized
[ https://issues.apache.org/jira/browse/KAFKA-19471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Schofield resolved KAFKA-19471.
--------------------------------------
Resolution: Fixed
> Enable acknowledgement for a record which could not be deserialized
> -------------------------------------------------------------------
>
> Key: KAFKA-19471
> URL: https://issues.apache.org/jira/browse/KAFKA-19471
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Andrew Schofield
> Assignee: Lan Ding
> Priority: Major
> Fix For: 4.2.0
>
>
> If a record fetched by a share consumer fails to be deserialized, the KIP states that it is automatically released and that the application cannot override this behavior. Actually, experience with KafkaShareConsumer shows that it would be helpful to be able to override this to REJECT such records instead.
> We can add an override `KafkaShareConsumer.acknowledge(String topic, int partition, long offset, AcknowledgeType type)` for this purpose where the user does not have a `ConsumerRecord` instance available, but they do know the topic, partition and offset from the DeserializationException. The validation of this information is exactly the same as for the same information when it is implied by the `ConsumerRecord`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)