[
https://issues.apache.org/jira/browse/HIVE-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-5726:
------------------------------
Description:
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).
was:
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).
> 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
>
> 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)
