Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/3648
Thanks for your contribution @haohui and the review @StephanEwen. Changes
look good to me. Merging this PR.
---
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/3648
+1 to merge this
---
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,
Github user haohui commented on the issue:
https://github.com/apache/flink/pull/3648
Totally Agree :-) @StephanEwen please take another look.
---
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
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3648
Good fix, thanks @haohui
I was wondering - I am a trying to advocate fewer dependencies in Flink
(there is always the problem of shading and conflicts) so if there is a way to
do this
Github user haohui commented on the issue:
https://github.com/apache/flink/pull/3648
The test failure seems unrelated. Cannot reproduce locally.
---
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
Github user haohui commented on the issue:
https://github.com/apache/flink/pull/3648
The failed tests are being addressed in FLINK-6175.
---
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
