[ https://issues.apache.org/jira/browse/HIVE-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergio Peña updated HIVE-7373: ------------------------------ Status: Open (was: Patch Available) decimal_trailing.q failed after I rebase origin/trunk (9be9bd7f663e421f9f50cb3b3bc054b7eb9ef647). I am canceling this patch to upload a new one. > Hive should not remove trailing zeros for decimal numbers > --------------------------------------------------------- > > Key: HIVE-7373 > URL: https://issues.apache.org/jira/browse/HIVE-7373 > Project: Hive > Issue Type: Bug > Components: Types > Affects Versions: 0.13.1, 0.13.0 > Reporter: Xuefu Zhang > Assignee: Sergio Peña > Attachments: HIVE-7373.1.patch, HIVE-7373.2.patch, HIVE-7373.3.patch, > HIVE-7373.4.patch, HIVE-7373.5.patch, HIVE-7373.6.patch > > > Currently Hive blindly removes trailing zeros of a decimal input number as > sort of standardization. This is questionable in theory and problematic in > practice. > 1. In decimal context, number 3.140000 has a different semantic meaning from > number 3.14. Removing trailing zeroes makes the meaning lost. > 2. In a extreme case, 0.0 has (p, s) as (1, 1). Hive removes trailing zeros, > and then the number becomes 0, which has (p, s) of (1, 0). Thus, for a > decimal column of (1,1), input such as 0.0, 0.00, and so on becomes NULL > because the column doesn't allow a decimal number with integer part. > Therefore, I propose Hive preserve the trailing zeroes (up to what the scale > allows). With this, in above example, 0.0, 0.00, and 0.0000 will be > represented as 0.0 (precision=1, scale=1) internally. -- This message was sent by Atlassian JIRA (v6.2#6252)