Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3832
Merging ...
---
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
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3832
+1 for 1.4 - just spent some good time cleaning up dependencies (also from
Hadoop) and this will almost certainly require to do another such pass...
---
If your project is set up for it, you
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3832
@rmetzger +1, agree that these changes are best made at the beginning of
the release cycle.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user rmetzger commented on the issue:
https://github.com/apache/flink/pull/3832
I personally think we should not include this into the 1.3 release.
Hadoop 2.8 most likely has new or changed dependencies, with different
transitive deps and so on. This can cause issues with
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3832
@StephanEwen changes made, and I rebased back a few commits for stable
tests and also made yarn-tests non-optional.
---
If your project is set up for it, you can reply to this email and have your
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3832
I think the convenience binaries are fine. From my side, we can drop
convenience builds for Hadoop 2.3 builds in Flink 1.3
Concerning the dependency management entry for `http*`- I think
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3832
@rmetzger @StephanEwen thoughts on releasing 2.8 binaries for Flink 1.3?
Are there old versions we can drop for 1.4?
---
If your project is set up for it, you can reply to this email and have
