[
https://issues.apache.org/jira/browse/KAFKA-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boyang Chen updated KAFKA-9776:
-------------------------------
Summary: Producer could automatically downgrade TxnOffsetCommitRequest with
internal flag (was: Producer should automatically downgrade
TxnOffsetCommitRequest)
> Producer could automatically downgrade TxnOffsetCommitRequest with internal
> flag
> --------------------------------------------------------------------------------
>
> Key: KAFKA-9776
> URL: https://issues.apache.org/jira/browse/KAFKA-9776
> Project: Kafka
> Issue Type: Improvement
> Components: producer
> Affects Versions: 2.6.0
> Reporter: Matthias J. Sax
> Assignee: Boyang Chen
> Priority: Critical
>
> When using transactions with a 2.5 producer against 2.4 (or older) brokers,
> it is not possible to call `producer.commitTransaction(...,
> ConsumerGroupMetadata)` but only the old API `producer.commitTransaction(...,
> String applicationId)` is supported.
> This implies that a developer needs to know the broker version when writing
> an application or write additional code to call the one or the other API
> depending on the broker version (the developer would need to write code to
> figure out the broker version, too).
> We should change the producer to automatically downgrade to the older
> TxnOffsetCommitRequest if `commitTransaction(..., ConsumerGroupMetadata)` is
> used against older brokers to avoid an `UnsupportedVersionException`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)