GitHub user twalthr opened a pull request:
https://github.com/apache/flink/pull/986
[FLINK-2447] [java api] TypeExtractor returns wrong type info when a Tuple
has two fields of the same POJO type
This fixes FLINK-2447 and simplifies the TypeExtractor a little bit.
Actually, the `alreadySeen` variable was unneccessary. The `typeHierarchy`
can be easily used for that. I think the problem was that the POJO-feature
developers didn't know the concept behind the `typeHierarchy` parameter. I
added a notice so that those bugs (hopefully) don't happen again.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/twalthr/flink PojoTypeExtrBug
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/986.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #986
----
commit e05081dc4c445cc13fbe1addaf433cd354a50dc9
Author: twalthr <[email protected]>
Date: 2015-08-04T13:30:28Z
[FLINK-2447] [java api] TypeExtractor returns wrong type info when a Tuple
has two fields of the same POJO type
----
---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
