Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 6 Nov 2013 03:08:17 +0000 (UTC)
From: "Xuefu Zhang (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12677108.1383325069743.25938.1383707297638@arcas>
In-Reply-To: <JIRA.12677108.1383325069743@arcas>
References: <JIRA.12677108.1383325069743@arcas>
Subject: [jira] [Updated] (HIVE-5726) The DecimalTypeInfo instance
 associated with a decimal constant is not in line with the precision/scale
 of the constant
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xuefu Zhang updated HIVE-5726:
------------------------------

    Attachment: HIVE-5726.2.patch

Patch #4 updated based on RB feedback.

> The DecimalTypeInfo instance associated with a decimal constant is not in line with the precision/scale of the constant
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-5726
>                 URL: https://issues.apache.org/jira/browse/HIVE-5726
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>         Attachments: HIVE-5726.1.patch, HIVE-5726.2.patch, HIVE-5726.patch
>
>
> Currently Hive uses a default decimal type info instance to associate with a decimal constant in the expression tree. To precisely determine the precision/scale of the expression result requires more accurate precision/scale of the type of the decimal constant. Thus, Hive uses a precision/scale of the constant for the type info instance. As an example, the following is not desirable:
> {code}
> hive> create table mytable as select 3.14BD as t from person_age limit 1;
> hive> desc mytable;
> OK
> t                   	decimal(65,30)      	None                
> Time taken: 0.08 seconds, Fetched: 1 row(s)
> {code}
> instead, the precision/scale for t above should be (3, 2).


--
This message was sent by Atlassian JIRA
(v6.1#6144)