[
https://issues.apache.org/jira/browse/KAFKA-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Chen updated KAFKA-13598:
------------------------------
Description:
In KAFKA-10619, we enabled idempotence by default. But we didn't update the
config validator, so that we can create producers with `idempotence` enabled
and `acks` = 1 or `retries` = 0.
Furthermore, I found although we made the `enable.idempotence` default to true,
there are many places in producer, we still take `enable.idempotence` as false
if user didn't "explicitly" set the config.
was:
In KAFKA-10619, we enabled idempotence by default. But we didn't update the
config validator, so that we can create producers with `idempotence` enabled
and `acks` = 1 or `retries` = 0.
> producer config didn't throw exception when retries and acks config changed
> ---------------------------------------------------------------------------
>
> Key: KAFKA-13598
> URL: https://issues.apache.org/jira/browse/KAFKA-13598
> Project: Kafka
> Issue Type: Bug
> Components: clients, config
> Affects Versions: 3.1.0, 3.0.0
> Reporter: Luke Chen
> Assignee: Luke Chen
> Priority: Major
>
> In KAFKA-10619, we enabled idempotence by default. But we didn't update the
> config validator, so that we can create producers with `idempotence` enabled
> and `acks` = 1 or `retries` = 0.
>
> Furthermore, I found although we made the `enable.idempotence` default to
> true, there are many places in producer, we still take `enable.idempotence`
> as false if user didn't "explicitly" set the config.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
