You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Justine Olshan (Jira)" <ji...@apache.org> on 2023/05/04 17:29:00 UTC

[jira] [Resolved] (KAFKA-14916) Fix code that assumes transactional ID implies all records are transactional

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

Justine Olshan resolved KAFKA-14916.
------------------------------------
    Resolution: Fixed

> Fix code that assumes transactional ID implies all records are transactional
> ----------------------------------------------------------------------------
>
>                 Key: KAFKA-14916
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14916
>             Project: Kafka
>          Issue Type: Sub-task
>    Affects Versions: 3.6.0
>            Reporter: Justine Olshan
>            Assignee: Justine Olshan
>            Priority: Blocker
>
> KAFKA-14561 wrote code that assumed that if a transactional ID was included, all record batches were transactional and had the same producer ID.
> This work with improve validation and fix the code that assumes all batches are transactional.
> Further, KAFKA-14561 will not assume all records are transactional.
> Originally this ticket had an action item to ensure all the producer IDs are the same in the batches since we send a single txn ID, but that can be done in a followup KAFKA-14958, as we still need to assess if we can enforce this without breaking workloads.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)