[
https://issues.apache.org/jira/browse/FLINK-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872883#comment-16872883
]
vinoyang commented on FLINK-12976:
----------------------------------
I can make sure that there are compatibility issues when bumping Kafka client
version from 2.2.0 to 2.3.0
log details: [https://api.travis-ci.org/v3/job/550192082/log.txt]
One of them is the {{FlinkKafkaInternalProducer}} uses reflection to get the
direct inner {{nextSequence}} field of {{TransactionManager}}.
Before 2.3.0, the type of this field is:
{code:java}
private final Map<TopicPartition, Integer> nextSequence;
{code}
How in 2.3.0, the {{TransactionManager}} changed its implementation, it
introduced two inner classes, named {{TopicPartitionBookkeeper}} and
{{TopicPartitionEntry}}. And the {{nextSequence}} is put into
{{TopicPartitionEntry}}.
So we need to change the way of getting this field. I will try to figure it
out. cc [~aljoscha] and [~pnowojski].
> Bump Kafka client version to 2.3.0 for universal Kafka connector
> ----------------------------------------------------------------
>
> Key: FLINK-12976
> URL: https://issues.apache.org/jira/browse/FLINK-12976
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Kafka
> Reporter: vinoyang
> Assignee: vinoyang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Recently, Kafka 2.3.0 has released, see here:
> [https://www.apache.org/dist/kafka/2.3.0/RELEASE_NOTES.html]
> We'd better bump the dependency version of Kafka client to 2.3.0 to track the
> newest version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
