Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/3562
Closing in favour of #3603
---
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
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/3562
Done. Re-opened at #3603.
---
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
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/3562
@aljoscha sure, I'll do that.
---
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
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/3562
@tzulitai I would suggest you open a PR with two commits: mine and your
changes on top. What do you think? Then I would close this PR.
---
If your project is set up for it, you can reply to this
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/3562
Here's my follow-up fixes for this:
https://github.com/tzulitai/flink/tree/FLINK-6018
It also includes a rebase for the merge conflict + test fixes.
We can continue with this after
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/3562
@aljoscha I've been trying out this PR to also test some Kryo behaviours. I
can address the above comments along the way and open a PR against this one :-)
---
If your project is set up for it,
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/3562
+1 to the rename. I was thinking the same here :-)
---
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
