[
https://issues.apache.org/jira/browse/HIVE-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15536856#comment-15536856
]
Gopal V commented on HIVE-13098:
--------------------------------
bq. However that would only work in queries, not for automated
pipelines/writers.
There's already a config for this problem for SQOOP, right?
{{sqoop.bigdecimal.format.string}}?
> 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, HIVE-13098.WIP2.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)
