[
https://issues.apache.org/jira/browse/PIG-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472819#comment-13472819
]
Dmitriy V. Ryaboy commented on PIG-2951:
----------------------------------------
I don't think killing whole jobs by throwing an exception on a single case of
overflow is good.
How about we increment a counter instead, and use the appropriate max or min
value as a result instead?
(eg, mysql in non-strict mode uses max_int if you insert 2*max+int)
> Overflow, Underflow errors
> --------------------------
>
> Key: PIG-2951
> URL: https://issues.apache.org/jira/browse/PIG-2951
> Project: Pig
> Issue Type: Bug
> Components: impl
> Affects Versions: 0.0.0, 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0,
> 0.8.0, 0.8.1, 0.9.0, 0.9.1, 0.9.2, 0.10.0
> Reporter: Ashutosh Chauhan
> Assignee: Ashutosh Chauhan
> Attachments: pig-2951.patch
>
>
> With very large (or very small) integer values there is a possibility of
> overflow (or underflow) errors. Worse thing is instead of failing, this
> currently results in incorrect results being returned, thereby leaving user
> with no clue that some of the tuples may have wrong value.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
