[jira] [Commented] (HIVE-13096) Cost to choose side table in MapJoin conversion based on cumulative cardinality

["Ashutosh Chauhan (JIRA)" <ji...@apache.org>]

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

Ashutosh Chauhan commented on HIVE-13096:
-----------------------------------------

This heuristic change should have supposedly impacted only selection of table chosen for streaming, and not change shape of tez dag. Is that expected ?

> Cost to choose side table in MapJoin conversion based on cumulative cardinality
> -------------------------------------------------------------------------------
>
>                 Key: HIVE-13096
>                 URL: https://issues.apache.org/jira/browse/HIVE-13096
>             Project: Hive
>          Issue Type: Bug
>          Components: Physical Optimizer
>    Affects Versions: 2.0.0, 2.1.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>         Attachments: HIVE-13096.01.patch, HIVE-13096.02.patch, HIVE-13096.03.patch, HIVE-13096.patch
>
>
> HIVE-11954 changed the logic to choose the side table in the MapJoin conversion algorithm. Initial heuristic for the cost was based on number of heavyweight operators.
> This extends that work so the heuristic is based on accumulate cardinality. In the future, we should choose the side based on total latency for the input.



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