[jira] [Comment Edited] (KAFKA-14687) Possible issue on documentation : producerConfig -> retries

["Ahmed Toumi (Jira)" <ji...@apache.org>]

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

Ahmed Toumi edited comment on KAFKA-14687 at 2/7/23 11:33 PM:
--------------------------------------------------------------

I see that was fixed at this revision number : d2556e02a25af28cf4cc093a190cc0154145121e

[https://github.com/apache/kafka/commit/d2556e02a25af28cf4cc093a190cc0154145121e]

But not yet update on the website

 

 


was (Author: 2me):
I see that was fixed at this revision number : d2556e02a25af28cf4cc093a190cc0154145121e

 

[https://github.com/apache/kafka/commit/d2556e02a25af28cf4cc093a190cc0154145121e]

 

> Possible issue on documentation : producerConfig -> retries
> -----------------------------------------------------------
>
>                 Key: KAFKA-14687
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14687
>             Project: Kafka
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 3.3.2
>            Reporter: Ahmed Toumi
>            Priority: Major
>
> Since Kafka 3, The documentation said [here|https://kafka.apache.org/documentation/#producerconfigs_retries] that
> {code:java}
> Allowing retries while setting enable.idempotence to false and max.in.flight.requests.per.connection to 1 will potentially change the ordering of records because if two batches are sent to a single partition, and the first fails and is retried but the second succeeds, then the records in the second batch may appear first. {code}
>  
>  
> Or I think that a "without" is missing
> Allowing retries while setting enable.idempotence to false and max.in.flight.requests.per.connection to 1 will potentially change the ordering of records
> Should be
>  
> Allowing retries while setting enable.idempotence to false and +*without setting*+ max.in.flight.requests.per.connection to 1 will potentially change the ordering of records



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