AHeise commented on pull request #17521: URL: https://github.com/apache/flink/pull/17521#issuecomment-953819233
I must admit that I still haven't fully understood the use case and the solution. Each application bundles the connectors. Say application A is using Kafka 2.4 and application B is using Kafka 2.6. Now I can run both applications in the same cluster without any issues afaik, as both are executed in separate class loaders. That's the state of Flink since a couple of versions already. With your proposal, application A may now use multiple classloaders but it can still only bundle one Kafka version. So I don't see the added value. We would need to add something like a jar in jar approach, where several Kafka versions are bundled. That could be implemented in the application jar entirely. Then the question is: is it worth it? How often does one specific application have conflicting connector versions? For most use cases, it does not seem to matter. There are very large Flink cluster installation, where the current approach seems to be sufficient. I'm probably overlooking something basic here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
