hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16100) Dynamic Sorted Partition optimizer loses sibling operators
Date Mon, 06 Mar 2017 07:52:32 GMT

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

Prasanth Jayachandran commented on HIVE-16100:
----------------------------------------------

I am missing something here. Under what scenario does FS's parent will have another sibling?
If it is multi file sink, then this optimization should be visited for each FSOp and each
path should have a SEL.

I am assuming the case you are describing is something like below. I am not sure if we will
end up with 
such plan.

{code}
RS -> SEL -> FS
      |
       -> FS
{code}

I tried running the query without the patch and it generated the same explain plan. 

> 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.2.0, 2.1.1
>            Reporter: Gopal V
>            Assignee: Gopal V
>         Attachments: HIVE-16100.1.patch, HIVE-16100.2.patch, HIVE-16100.2.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
(v6.3.15#6346)

Mime
View raw message