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

Zoltan Haindrich edited comment on HIVE-24486 at 12/18/20, 12:30 PM:
---------------------------------------------------------------------

I've attached an  image  (o.1.full.png) where redundant vertices can be 
identified 

cluster 11 and 13 could be merged 

right now I'm not sure if the original idea could face all kind of issues - 
because the iterative merge would require the plan to be executable after each 
step; however after merging the 2 RS operators the 2 vertices will become "one" 
and the new vertex will have a parallel edge to cluster 10 which is not 
permitted....

I think there is another angle from which this could be tackled: identify 
redunant vertices somehow (probably by using operator signatures)




was (Author: kgyrtkirk):
I've attached an image  where redundant vertices can be identified 
!o.1.full.png!

cluster 11 and 13 could be merged 

right now I'm not sure if the original idea could face all kind of issues - 
because the iterative merge would require the plan to be executable after each 
step; however after merging the 2 RS operators the 2 vertices will become "one" 
and the new vertex will have a parallel edge to cluster 10 which is not 
permitted....

I think there is another angle from which this could be tackled: identify 
redunant vertices somehow (probably by using operator signatures)



> Enhance operator merge logic to also consider going thru RS operators
> ---------------------------------------------------------------------
>
>                 Key: HIVE-24486
>                 URL: https://issues.apache.org/jira/browse/HIVE-24486
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>         Attachments: o.1.full.png
>
>
> the targeted situation looks like this:
> {code}
> OP1 -> RS1.1 -> JOIN1.1
> OP1 -> RS1.2 -> JOIN1.2 
> OP2 -> RS2.1 -> JOIN1.1 -> RS3.1 
> OP2 -> RS2.2 -> JOIN1.2 -> RS3.2 
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to