You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Paul Lin (JIRA)" <ji...@apache.org> on 2018/12/11 04:28:00 UTC
[jira] [Closed] (FLINK-10943) Flink runtime test failed caused by
curator dependency conflicts
[ https://issues.apache.org/jira/browse/FLINK-10943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Lin closed FLINK-10943.
----------------------------
Resolution: Not A Bug
> Flink runtime test failed caused by curator dependency conflicts
> ----------------------------------------------------------------
>
> Key: FLINK-10943
> URL: https://issues.apache.org/jira/browse/FLINK-10943
> Project: Flink
> Issue Type: Bug
> Components: Build System, Tests
> Affects Versions: 1.5.5, 1.6.2
> Reporter: Paul Lin
> Assignee: Paul Lin
> Priority: Minor
> Labels: pull-request-available
> Attachments: org.apache.flink.runtime.zookeeper.ZooKeeperStateHandleStoreTest.txt
>
>
> Hadoop-common of 2.6 + version includes curator dependencies, which would have conflicts with the curator used by Flink runtime and cause test failures (the attachment is the surefire report).
> The curator dependencies tree of flink runtime is as below:
> ```
> flink-shaded-hadoop2 -> hadoop-common -> curator-client & curator-recipes
> flink-shaded-curator -> curator-recipes -> curator-framework -> curator-client
> ```
> According to the dependency mechanism, maven would pick the curator-client in flink-shaded-hadoop2, and curator-framework and curator-recipes from flink-shaded-curator.
> To fix the problem I think we can simply exclude curator-client from flink-shaded-hadoop2 dependency in flink-runtime.
> I'd like to fix this, please let me know what you think. Thanks!
> [^org.apache.flink.runtime.zookeeper.ZooKeeperStateHandleStoreTest.txt]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)