Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/1045#issuecomment-135370839
@StephanEwen yes, generally InvalidTypesExceptions are not propagated,
except TypeExtractor.getInfoFor(Class ...), which is both public and used in
the TypeExtractor.
If an operator that can't tolerate MissingTypeInfo is given one, when will
it fail?
There are basically 2 options that i see:
* keep returning a MissingTypeInfo, but go through call to TypeExtractor
methods and add a check for MissingTypeInfo if necessary
* throw a checked exception instead of returning a MissingTypeInfo, and go
through every call to TypeExtractor methods and add try/catch blocks.
essentially both options are the same, so do we prefer an exception or a
MissingTypeInfo?
either way, we're gonna need a lot more changes :/
---
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.
---
