[
https://issues.apache.org/jira/browse/FLINK-24420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460043#comment-17460043
]
Timo Walther commented on FLINK-24420:
--------------------------------------
I would vote for OVERFLOW for the legacy mode and FAIL for the non legacy one.
But only for the non legacy one, the behavior is configurable.
> Casting to a "narrower" type doesn't throw exception but follows Java overflow
> ------------------------------------------------------------------------------
>
> Key: FLINK-24420
> URL: https://issues.apache.org/jira/browse/FLINK-24420
> Project: Flink
> Issue Type: Sub-task
> Reporter: Marios Trivyzas
> Priority: Major
>
> Ideally we should provide config option to be able to keep current behaviour
> where such casts follow the standard Java overflow, but in order to avoid
> "hidden" erroneous behaviour the user should be able to have an error thrown
> when an overflow happens. So basically range checks for each type like
> TINYINT, SMALLINT, INT, FLOAT should be enforced. Keep in mind of such range
> checks for every conversion would add performance overhead.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
