You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Boyang Chen (Jira)" <ji...@apache.org> on 2020/01/19 00:51:00 UTC

[jira] [Updated] (KAFKA-9453) Make transaction.id optional in group mode EOS

     [ https://issues.apache.org/jira/browse/KAFKA-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boyang Chen updated KAFKA-9453:
-------------------------------
    Description: 
After 447, one of the big improvement is that we are no longer requiring single writer scope guarantee, so that user doesn't have to configure a unique transactional.id for transaction safety.

In fact, without security concern, we could even avoid using initTransaction API as well.

  was:After 447, one of the big improvement is that we are no longer requiring single writer scope guarantee, so that user doesn't have to configure a unique transactional.id for transaction safety.


> Make transaction.id optional in group mode EOS
> ----------------------------------------------
>
>                 Key: KAFKA-9453
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9453
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Boyang Chen
>            Priority: Major
>
> After 447, one of the big improvement is that we are no longer requiring single writer scope guarantee, so that user doesn't have to configure a unique transactional.id for transaction safety.
> In fact, without security concern, we could even avoid using initTransaction API as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)