[ 
https://issues.apache.org/jira/browse/HIVE-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814806#comment-13814806
 ] 

Hive QA commented on HIVE-5726:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12612312/HIVE-5726.2.patch

{color:green}SUCCESS:{color} +1 4552 tests passed

Test results: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/146/testReport
Console output: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/146/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12612312

> 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)

Reply via email to