[
https://issues.apache.org/jira/browse/HIVE-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692374#comment-16692374
]
Hive QA commented on HIVE-20940:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12948751/HIVE-20940.02.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/14994/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14994/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14994/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12948751/HIVE-20940.02.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12948751 - PreCommit-HIVE-Build
> Bridge cases in which Calcite's type resolution is more stricter than Hive.
> ---------------------------------------------------------------------------
>
> Key: HIVE-20940
> URL: https://issues.apache.org/jira/browse/HIVE-20940
> Project: Hive
> Issue Type: Bug
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Attachments: HIVE-20940.01.patch, HIVE-20940.01.patch,
> HIVE-20940.02.patch
>
>
> Calcite is more stricter w.r.t common types than Hive.
> For example in case a CASE with different types on the branches is not
> something Calcite likes:
> {code}
> CASE
> WHEN cond1 THEN booleanCol
> WHEN cond2 THEN stringCol
> WHEN cond3 THEN floatCol
> ELSE doubleCol
> END
> {code}
> issues will only happen with 1.18-SNAPSHOT version
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
