You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ahmed Toumi (Jira)" <ji...@apache.org> on 2023/02/07 11:37:00 UTC
[jira] [Created] (KAFKA-14687) Possible issue on documentation : producerConfig -> retries
Ahmed Toumi created KAFKA-14687:
-----------------------------------
Summary: 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
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)