[
https://issues.apache.org/jira/browse/KAFKA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021295#comment-16021295
]
Damian Guy commented on KAFKA-5308:
-----------------------------------
[~hachikuji] i think this may not be possible once
https://github.com/apache/kafka/pull/3103/files is merged? i.e., in
{{handleAddPartitionToTxnRequest}} we will check if any of the topics are on
unsupported message format and respond with an
{{Errors.UNSUPPORTED_FOR_MESSAGE_FORMAT}}
> TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMarker response
> --------------------------------------------------------------------------
>
> Key: KAFKA-5308
> URL: https://issues.apache.org/jira/browse/KAFKA-5308
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, core, producer
> Reporter: Jason Gustafson
> Assignee: Damian Guy
> Priority: Blocker
> Labels: exactly-once
> Fix For: 0.11.0.0
>
>
> It could be the case that one of the topics added to a transaction is on a
> lower message format version. Because of
> https://github.com/apache/kafka/pull/3118, the producer won't be able to send
> any data to that topic, but the TC will nevertheless try to write the
> commit/abort marker to the log. Like the Produce request, the WriteTxnMarker
> request should return the UNSUPPORTED_FOR_MESSSAGE_FORMAT error. Instead of
> retrying, we should log a warning and remove the partition from the set of
> partitions awaiting marker completion.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
