[jira] [Comment Edited] (KAFKA-13598) producer config didn't throw exception when retries and acks config changed

["David Jacot (Jira)" <ji...@apache.org>]

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

David Jacot edited comment on KAFKA-13598 at 1/18/22, 5:55 PM:
---------------------------------------------------------------

That seems to be a bug and not a regression introduced in 3.1 so I lean towards fixing it in 3.0.1 and 3.1.1. What do you guys think? I will take a close look into it tomorrow.


was (Author: dajac):
That seems to be a bug and not a regression introduced in 3.1 so I lean towards fixing it in 3.0.1 and 3.1.1. What do you guys think?

> 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
>             Fix For: 3.0.1
>
>
> 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)