You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2016/04/25 21:07:13 UTC

[jira] [Updated] (PIG-4785) Optimize multi-query plan for diamond shape edges

     [ https://issues.apache.org/jira/browse/PIG-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rohini Palaniswamy updated PIG-4785:
------------------------------------
    Fix Version/s:     (was: 0.16.0)
                   0.17.0

> Optimize multi-query plan for diamond shape edges
> -------------------------------------------------
>
>                 Key: PIG-4785
>                 URL: https://issues.apache.org/jira/browse/PIG-4785
>             Project: Pig
>          Issue Type: Sub-task
>          Components: tez
>            Reporter: Rohini Palaniswamy
>            Assignee: Rohini Palaniswamy
>             Fix For: 0.17.0
>
>
>   If diamond shaped edge (two edges going to same vertex), we do not merge into Split. Lot of data is transferred because of that. It can be optimized to merge the operator into the Split, but still have a POValueInputTez->POValueOutputTez vertex which just will be used to redirect the input to avoid the diamond shaped edge.  This will allow filtering and other processing to happen in the Split operator itself and the data transferred to the routing vertex will be minimal.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)