flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tillrohrmann <...@git.apache.org>
Subject [GitHub] flink issue #4120: [FLINK-6836] [tests] Fix YARNSessionCapacitySchedulerITCa...
Date Thu, 15 Jun 2017 09:43:34 GMT
Github user tillrohrmann commented on the issue:

    https://github.com/apache/flink/pull/4120
  
    I first thought I had to downgrade, because of the aforementioned problem. However, Hadoop
2.8.0 needs at least httpclient `4.5.2`. Luckily, they fixed the problem with the `URLEncodedUtils#parse`
method in `4.5.3`. Therefore I bumped the version again.
    
    Concerning moving the dependency management to `flink-shaded-hadoop`: I think this is
unfortunately not possible since due the immutable reactor builds from maven, `flink-yarn-tests`
pulls all dependencies from `flink-shaded-hadoop` and `flink-shaded-yarn-tests`. This also
means that depending on the classpath order, we either use the shaded Yarn mini-cluster or
not. In the latter case we have to make sure that we are using `httpclient` `4.5.3` which
is only the case if we define the dependency management in the parent pom.
    
    As a side remark, given this situation with maven, I'm not sure whether we actually need
the `flink-shaded-yarn-tests` module.
    
    A proper solution would be fixing the problem with the immutable builds. For example,
everything works properly if we first install the shaded jars and then build the flink-yarn-tests.
Then maven will properly resolve all dependencies. In this case, I think it should be possible
to move the dependency management into `flink-shaded-hadoop`.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message