[
https://issues.apache.org/jira/browse/KAFKA-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175504#comment-16175504
]
ASF GitHub Bot commented on KAFKA-5913:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/3878
> Add RecordMetadataNotAvailableException to indicate that ProduceResponse did
> not contain offset and timestamp information
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-5913
> URL: https://issues.apache.org/jira/browse/KAFKA-5913
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Apurva Mehta
> Assignee: Apurva Mehta
> Fix For: 1.0.0
>
>
> One of the changes in KIP-192 is to send a {{DUPLICATE_SEQUENCE}} error code
> with a {{ProduceResponse}} when we detect a duplicate on the broker but don't
> have the batch metadata for the sequence in question in memory.
> To handle this on the client, we mark the batch as successful, but cannot
> return the offset and timestamp information in the {{RecordMetadata}}
> returned in the produce future. Instead of returning implicit invalid values
> (like -1), we should throw a {{RecordMetadataNotAvailableException}} to
> ensure that applications don't suffer from faulty processing.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
