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

Hive QA commented on HIVE-6568:
-------------------------------



{color:red}Overall{color}: -1 at least one tests failed

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

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 5375 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.ql.exec.vector.expressions.TestVectorTypeCasts.testCastDecimalToString
org.apache.hive.service.cli.TestEmbeddedThriftBinaryCLIService.testExecuteStatementAsync
{noformat}

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12633603

> Vectorized cast of decimal to string and timestamp produces incorrect result.
> -----------------------------------------------------------------------------
>
>                 Key: HIVE-6568
>                 URL: https://issues.apache.org/jira/browse/HIVE-6568
>             Project: Hive
>          Issue Type: Bug
>          Components: Vectorization
>    Affects Versions: 0.13.0
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HIVE-6568.1.patch, HIVE-6568.2.patch
>
>
> A decimal value 1.23 with scale 5 is represented in string as 1.23000. This 
> behavior is different from HiveDecimal behavior.
> The difference in cast to timestamp is due to more aggressive rounding in 
> vectorized expression.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to