You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2017/04/04 15:53:41 UTC
[jira] [Resolved] (IMPALA-43) Impala needs to log numeric overflow
errors
[ https://issues.apache.org/jira/browse/IMPALA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-43.
---------------------------------
Resolution: Duplicate
> Impala needs to log numeric overflow errors
> -------------------------------------------
>
> Key: IMPALA-43
> URL: https://issues.apache.org/jira/browse/IMPALA-43
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 0.1, Impala 1.3, Impala 1.4, Impala 2.0, Impala 2.1, Impala 2.2
> Reporter: Nong Li
> Priority: Minor
> Labels: ramp-up, supportability, usability
>
> Impala should log when values overflow. We probably don't want to log each value, that could be very many values.
> This is most useful on the scanner path. For example, we had one table where the schema was int (int32) when it should have been bigint (int64). This resulted in a hard to diagnose duplicate unique id issue. It would have been much better if we just logged something like "1 billion values overflowed for col x"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)