[
https://issues.apache.org/jira/browse/HIVE-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010122#comment-17010122
]
Hive QA commented on HIVE-22510:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12990122/HIVE-22510.18.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 17859 tests
executed
*Failed tests:*
{noformat}
org.apache.hive.jdbc.TestRestrictedList.org.apache.hive.jdbc.TestRestrictedList
(batchId=288)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/20102/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/20102/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-20102/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12990122 - PreCommit-HIVE-Build
> Support decimal64 operations for column operands with different scales
> ----------------------------------------------------------------------
>
> Key: HIVE-22510
> URL: https://issues.apache.org/jira/browse/HIVE-22510
> Project: Hive
> Issue Type: Bug
> Reporter: Ramesh Kumar Thangarajan
> Assignee: Ramesh Kumar Thangarajan
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-22510.11.patch, HIVE-22510.13.patch,
> HIVE-22510.14.patch, HIVE-22510.15.patch, HIVE-22510.16.patch,
> HIVE-22510.17.patch, HIVE-22510.18.patch, HIVE-22510.2.patch,
> HIVE-22510.3.patch, HIVE-22510.4.patch, HIVE-22510.5.patch,
> HIVE-22510.7.patch, HIVE-22510.9.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now, if the operands on the decimal64 operations are columns with
> different scales, then we do not use the decimal64 vectorized version and
> fall back to HiveDecimal vectorized version of the operator. In this Jira, we
> will check if we can use decimal64 vectorized version, even if the scales are
> different.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
