[
https://issues.apache.org/jira/browse/HIVE-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840964#comment-13840964
]
Hive QA commented on HIVE-5872:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12617321/HIVE-5872.4.patch
{color:green}SUCCESS:{color} +1 4458 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/537/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/537/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: 12617321
> Make UDAFs such as GenericUDAFSum report accurate precision/scale for decimal
> types
> -----------------------------------------------------------------------------------
>
> Key: HIVE-5872
> URL: https://issues.apache.org/jira/browse/HIVE-5872
> Project: Hive
> Issue Type: Improvement
> Components: Types, UDF
> Affects Versions: 0.12.0
> Reporter: Xuefu Zhang
> Assignee: Xuefu Zhang
> Attachments: HIVE-5872.1.patch, HIVE-5872.2.patch, HIVE-5872.3.patch,
> HIVE-5872.4.patch, HIVE-5872.patch
>
>
> Currently UDAFs are still reporting system default precision/scale (38, 18)
> for decimal results. Not only this is coarse, but also this can cause
> problems in subsequent operators such as division, where the result is
> dependent on the precision/scale of the input, which can go out of bound
> (38,38). Thus, these UDAFs should correctly report the precision/scale of the
> result.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
