[ 
https://issues.apache.org/jira/browse/FLINK-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shannon Carey updated FLINK-6805:
---------------------------------
    Description: 
The Flink Cassandra connector has a dependency on Netty libraries (via 
promotion of transitive dependencies by the Maven shade plugin) at version 
4.0.33.Final, which disagrees with the version included in Flink of 
4.0.27.Final which is included & managed by the parent POM via dependency on 
netty-all.

Due to use of netty-all, the dependency management doesn't take effect on the 
individual libraries such as netty-handler, netty-codec, etc.

I suggest that dependency management of Netty should be added for all Netty 
libraries individually (netty-handler, etc.) so that all Flink modules use the 
same version, and similarly I suggest that exclusions be added to the 
quickstart example POM for the individual Netty libraries so that fat JARs 
don't include conflicting versions of Netty.

It seems like this problem started when FLINK-6084 was implemented: transitive 
dependencies of the flink-connector-cassandra were previously omitted, and now 
that they are included we must make sure that they agree with the Flink 
distribution.

  was:
The Flink Cassandra connector has a dependency on Netty libraries (via 
promotion of transitive dependencies by the Maven shade plugin) at version 
4.0.33.Final, which disagrees with the version included in Flink of 
4.0.27.Final which is included & managed by the parent POM via dependency on 
netty-all.

Due to use of netty-all, the dependency management doesn't take effect on the 
individual libraries such as netty-handler, netty-codec, etc.

I suggest that dependency management of Netty should be added for all Netty 
libraries individually (netty-handler, etc.) so that all Flink modules use the 
same version, and similarly I suggest that exclusions be added to the 
quickstart example POM for the individual Netty libraries so that fat JARs 
don't include conflicting versions of Netty.


> Flink Cassandra connector dependency on Netty disagrees with Flink
> ------------------------------------------------------------------
>
>                 Key: FLINK-6805
>                 URL: https://issues.apache.org/jira/browse/FLINK-6805
>             Project: Flink
>          Issue Type: Bug
>          Components: Cassandra Connector
>    Affects Versions: 1.3.0, 1.2.1
>            Reporter: Shannon Carey
>
> The Flink Cassandra connector has a dependency on Netty libraries (via 
> promotion of transitive dependencies by the Maven shade plugin) at version 
> 4.0.33.Final, which disagrees with the version included in Flink of 
> 4.0.27.Final which is included & managed by the parent POM via dependency on 
> netty-all.
> Due to use of netty-all, the dependency management doesn't take effect on the 
> individual libraries such as netty-handler, netty-codec, etc.
> I suggest that dependency management of Netty should be added for all Netty 
> libraries individually (netty-handler, etc.) so that all Flink modules use 
> the same version, and similarly I suggest that exclusions be added to the 
> quickstart example POM for the individual Netty libraries so that fat JARs 
> don't include conflicting versions of Netty.
> It seems like this problem started when FLINK-6084 was implemented: 
> transitive dependencies of the flink-connector-cassandra were previously 
> omitted, and now that they are included we must make sure that they agree 
> with the Flink distribution.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to