You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2016/09/28 02:59:20 UTC

[jira] [Updated] (HIVE-13098) Add a strict check for when the decimal gets converted to null due to insufficient width

     [ https://issues.apache.org/jira/browse/HIVE-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Shelukhin updated HIVE-13098:
------------------------------------
    Attachment: HIVE-13098.WIP.patch

The epic WIP patch... still need to take care of some paths.

Propagating config to all decimals is difficult thanks to massive static use in Hive...

> Add a strict check for when the decimal gets converted to null due to insufficient width
> ----------------------------------------------------------------------------------------
>
>                 Key: HIVE-13098
>                 URL: https://issues.apache.org/jira/browse/HIVE-13098
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-13098.WIP.patch
>
>
> When e.g. 999999 is selected as decimal(5,0), the result is null. This can be problematic, esp. if the data is written to a table and lost without the user realizing it. There should be an option to error out in such cases instead; it should probably be on by default and the error message should instruct the user on how to disable it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)