You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2015/09/17 16:44:04 UTC
[jira] [Created] (FLINK-2693) Refactor InvalidTypesException to be
checked
Chesnay Schepler created FLINK-2693:
---------------------------------------
Summary: Refactor InvalidTypesException to be checked
Key: FLINK-2693
URL: https://issues.apache.org/jira/browse/FLINK-2693
Project: Flink
Issue Type: Improvement
Components: Java API
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
Priority: Minor
When the TypeExtractor fails, it generally throws an InvalidTypesException. This is currently an unchecked exception, although we sometimes recover from it, usually by creating a MissingTypeInfo manually.
Furthermore, the extractor can also throw IllegalArgumentExceptions in some cases. Figuring out which exception is thrown under which conditions is pretty tricky, causing issues such as FLINK-2557.
This should be rectified by
# making InvalidTypesException a checked exception
# only throwing an InvalidTypesException upon failure
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)