You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2019/07/04 12:49:00 UTC
[jira] [Closed] (FLINK-12902) Cleanup flink-yarn-tests dependencies
[ https://issues.apache.org/jira/browse/FLINK-12902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-12902.
------------------------------------
Resolution: Fixed
master: 1dff9e0d2082532422a8dc787ab49ffbd77c1bed
> Cleanup flink-yarn-tests dependencies
> -------------------------------------
>
> Key: FLINK-12902
> URL: https://issues.apache.org/jira/browse/FLINK-12902
> Project: Flink
> Issue Type: Improvement
> Components: Build System, Deployment / YARN
> Affects Versions: 1.9.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The dependency situation in this module is just insane; you have a few unshaded hadoop dependencies from `flink-yarn-tests`, some shaded hadoop dependencies from `flink-shaded-yarn-tests` and _yet another_ set of shaded hadoop dependencies from `flink-shaded-hadoop`. All of these are available on the test classpath, resulting in what is effectively an incomprehensible classpath.
> This is highlighted in the shading patterns in `flink-shaded-yarn-tests`, which absolutely had to be in sync with `flink-shaded-hadoop` as otherwise you ended up with strange `VerifyErrors`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)