Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.3.2
-
None
-
None
Description
Since Kafka 3, The documentation said here that
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.
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