[
https://issues.apache.org/jira/browse/HIVE-22578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990321#comment-16990321
]
Hive QA commented on HIVE-22578:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12987684/HIVE-22578.2.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 17760 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/19785/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/19785/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-19785/
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
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12987684 - PreCommit-HIVE-Build
> CBO genOPTree is not failsafe for CTAS and VIEW statements
> ----------------------------------------------------------
>
> Key: HIVE-22578
> URL: https://issues.apache.org/jira/browse/HIVE-22578
> Project: Hive
> Issue Type: Bug
> Components: CBO
> Affects Versions: 3.0.0, 3.1.2
> Reporter: Aron Hamvas
> Assignee: Aron Hamvas
> Priority: Major
> Fix For: 3.0.1, 3.1.3
>
> Attachments: HIVE-22578.2.patch, HIVE-22578.patch
>
>
> If CBO fails during OT generation, it is supposed to skip CBO and fall back
> to SemanticAnalyzer generating the OT for the original AST. However, for CTAS
> and VIEW statements, the original AST is discarded and replaced with the new
> AST.
> If OT generation for the new AST fails with a SemanticException, the
> compilation is destined to fail completely since we cannot fall back to the
> original and possibly valid AST.
> Also, the SemanticException sometimes gets hidden and misjudged as a missing
> column statistics issue due to bad error handling.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
