[
https://issues.apache.org/jira/browse/FLINK-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078558#comment-17078558
]
Piotr Nowojski edited comment on FLINK-15362 at 4/8/20, 6:13 PM:
-----------------------------------------------------------------
Yes, it looks you are right :( We could try some magic to disable
`transactionManager.beginAbort();` calls somehow, but ehh...
[~jqin] is there any chance we could push for proper two phase commit
implementation in Kafka?
Alternate approach would be to switch to WAL (it has it's own issues), or to
start maintaining our own implementation fo the KafkaProducer based on the
Kafka's REST API.
was (Author: pnowojski):
Yes, it looks you are right :( We could try some magic to disable
`transactionManager.beginAbort();` calls somehow, but ehh...
[~jqin] is there any chance we could push for proper two phase commit
implementation in Kafka?
> Bump Kafka client version to 2.4.0 for universal Kafka connector
> ----------------------------------------------------------------
>
> Key: FLINK-15362
> URL: https://issues.apache.org/jira/browse/FLINK-15362
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Reporter: vinoyang
> Assignee: Aljoscha Krettek
> Priority: Major
>
> Kafka 2.4 has been released recently. There are many features are involved in
> this version. More details:
> https://blogs.apache.org/kafka/entry/what-s-new-in-apache1
> IMO, it would be better to bump the Kafka client version to 2.4.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
