[GitHub] flink issue #2823: [FLINK-4872] [types] Type erasure problem exclusively on ...

2016-11-28 Thread twalthr
Github user twalthr commented on the issue: https://github.com/apache/flink/pull/2823 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 the

[GitHub] flink issue #2823: [FLINK-4872] [types] Type erasure problem exclusively on ...

2016-11-28 Thread StephanEwen
Github user StephanEwen commented on the issue: https://github.com/apache/flink/pull/2823 Looks good, +1 to merge --- 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] flink issue #2823: [FLINK-4872] [types] Type erasure problem exclusively on ...

2016-11-25 Thread twalthr
Github user twalthr commented on the issue: https://github.com/apache/flink/pull/2823 Thanks for the hint @StephanEwen. I improved the PR. --- 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] flink issue #2823: [FLINK-4872] [types] Type erasure problem exclusively on ...

2016-11-23 Thread StephanEwen
Github user StephanEwen commented on the issue: https://github.com/apache/flink/pull/2823 I think we can do a more solid approach to that. Would be good to not to rely on the context class loader. 1. You could use the classloader of the component type directly, i.e.,