You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Matt McCline (JIRA)" <ji...@apache.org> on 2018/08/30 04:57:00 UTC
[jira] [Assigned] (HIVE-13963) vectorization - string arguments may
be converted to decimal null
[ https://issues.apache.org/jira/browse/HIVE-13963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt McCline reassigned HIVE-13963:
-----------------------------------
Assignee: (was: Matt McCline)
> vectorization - string arguments may be converted to decimal null
> -----------------------------------------------------------------
>
> Key: HIVE-13963
> URL: https://issues.apache.org/jira/browse/HIVE-13963
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Priority: Major
>
> See HIVE-13957.
> The default precision and scale for the implicit decimal cast are -max,max, ie 38,38- 38,18. -Those don't do what the code may assume they do. All the values >=1- Some values may become invalid and precision-scale enforcement automatically converts them to null.
> We need to
> 1) Validate when this happens in/after the conversion code and bail;
> 2) Or, derive precision and scale from the constants themselves so they all fit, instead;
> 3) Or, derive it from the type of whatever caused the conversion in the first place (e.g. IN column decimal); however, this could be function-specific (e.g. IN just needs equality, BETWEEN would need at least one extra digit, arithmetic, if this ever happens, would need everything, etc.);
> 4) Something else? :)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)