Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/1759
---
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
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1759#issuecomment-192362699
Will 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
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1759#issuecomment-192200612
+1
to merge this into the 1.0 and 1.1 branches
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user chobeat commented on the pull request:
https://github.com/apache/flink/pull/1759#issuecomment-191857083
I tested it too and it works perfectly both on an example case and in the
code where the problem arose.
---
If your project is set up for it, you can reply to this
Github user gyfora commented on the pull request:
https://github.com/apache/flink/pull/1759#issuecomment-191821834
I tested it in my application where I was previously having both issues.
Now it works perfectly, thanks!
+1 from me :+1:
---
If your project is set up
GitHub user twalthr opened a pull request:
https://github.com/apache/flink/pull/1759
[FLINK-3566] [FLINK-3563] Input type validation improvements
This PR fixes issues with the input type validation.
[FLINK-3566] Custom type information have been interpreted as basic or
