[
https://issues.apache.org/jira/browse/FLINK-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler closed FLINK-4909.
-----------------------------------
Resolution: Won't Fix
The JDBC InputFormat no longer does any casts or type checks.
> JDBC Input format cast exception management
> -------------------------------------------
>
> Key: FLINK-4909
> URL: https://issues.apache.org/jira/browse/FLINK-4909
> Project: Flink
> Issue Type: Improvement
> Components: Batch Connectors and Input/Output Formats
> Affects Versions: 1.1.1
> Reporter: Stefano Bortoli
> Priority: Minor
>
> When setting the type settings for the JDBC Input Format one can easily make
> errors in setting the correct type (e.g. INT vs DECIMAL, or LONG vs
> BIG_DECIMAL)
> it would be nice to have the class cast Exception to return also the name of
> field causing the exception. In a sense, improve the exception message.
> For example: java.lang.ClassCastException: java.math.BigDecimal cannot be
> cast to java.lang.String *for field MY_BIGDECIMAL_FIELD*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
