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

Hive QA commented on HIVE-16100:
--------------------------------



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

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 15660 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/15266/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/15266/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-15266/

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: 12951403 - PreCommit-HIVE-Build

> Dynamic Sorted Partition optimizer loses sibling operators
> ----------------------------------------------------------
>
>                 Key: HIVE-16100
>                 URL: https://issues.apache.org/jira/browse/HIVE-16100
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Planning
>    Affects Versions: 1.2.1, 2.1.1, 2.2.0
>            Reporter: Gopal V
>            Assignee: Vineet Garg
>            Priority: Major
>         Attachments: HIVE-16100.1.patch, HIVE-16100.10.patch, 
> HIVE-16100.11.patch, HIVE-16100.12.patch, HIVE-16100.2.patch, 
> HIVE-16100.2.patch, HIVE-16100.3.patch, HIVE-16100.4.patch, 
> HIVE-16100.5.patch, HIVE-16100.6.patch, HIVE-16100.7.patch, 
> HIVE-16100.8.patch, HIVE-16100.9.patch
>
>
> https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/optimizer/SortedDynPartitionOptimizer.java#L173
> {code}
>       // unlink connection between FS and its parent
>       fsParent = fsOp.getParentOperators().get(0);
>       fsParent.getChildOperators().clear();
> {code}
> The optimizer discards any cases where the fsParent has another SEL child 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to