Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/249#issuecomment-70257415
I think that this one can go into the 0.9 master now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/249#issuecomment-70470401
+1
---
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 uce commented on the pull request:
https://github.com/apache/flink/pull/249#issuecomment-70645554
+1
I will merge this in the next batch.
---
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 proje
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/249#issuecomment-70702082
OK I've rebased this PR on the current master. All tests are running
locally (Travis is still flaky). @mxm is running some cluster tests. I'll push
to master after his OK. :-)
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/249#issuecomment-70758622
Cluster tests worked fine. If no one objects I'll merge this later today.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/249
---
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 enabl
