[
https://issues.apache.org/jira/browse/FLINK-18231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130381#comment-17130381
]
Dawid Wysakowicz commented on FLINK-18231:
------------------------------------------
Ad. 1 But the user needs to know which kafka client to add. Moreover she/he
needs to know which kafka client works with which flink connector. Plus needs
to know to use only the flink connector that there is a corresponding kafka
client on the classpath.
Ad. 2 IMO this contradicts with point 1. Nevertheless this would be an
improvement. Still I think it will not work out of the box, as the user must
ensure proper isolation of classloaders and that the corresponding flink
connector ends up in the same classloader as the kafka client. Wouldn't it be
better to load both the flink connector and corresponding kafka client
dynamically into a separate classloader in that case?
> flink kafka connector exists same qualified class name, whch will cause
> conflicts when user has all the versions of flink-kafka-connector
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-18231
> URL: https://issues.apache.org/jira/browse/FLINK-18231
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Affects Versions: 1.11.0
> Reporter: jackylau
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
>
> There are 0.9/0.10/0.11/2.x four version of kafka connector in 1.11
> There are 0.10/0.11/2.x three version of kafka connector in 1.12-snapshot
> But flink kafka connector exists same qualified class name such as
> KafkaConsumerThread and Handover whch will cause conflicts when i have all
> the versions of flink-kafka-connector.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
