[
https://issues.apache.org/jira/browse/HIVE-7613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139611#comment-14139611
]
Suhas Satish commented on HIVE-7613:
------------------------------------
{{ConvertJoinMapJoin}} heavily uses {{OptimizeTezProcContext}} . Although we do
have an equivalent {{OptimizeSparkProcContext}}, the 2 are not derived from any
common ancestor class. We will need some class hierarchy redesign/refactoring
to make ConvertJoinMapJoin be more generic to support multiple execution
frameworks.
For now, I am thinking of proceeding with a cloned {{SparkConvertJoinMapJoin}}
class using {{OptimizeSparkProcContext}}
We might need to open a jira for this refactoring.
> Research optimization of auto convert join to map join [Spark branch]
> ---------------------------------------------------------------------
>
> Key: HIVE-7613
> URL: https://issues.apache.org/jira/browse/HIVE-7613
> Project: Hive
> Issue Type: Sub-task
> Components: Spark
> Reporter: Chengxiang Li
> Assignee: Suhas Satish
> Priority: Minor
> Attachments: HIve on Spark Map join background.docx
>
>
> ConvertJoinMapJoin is an optimization the replaces a common join(aka shuffle
> join) with a map join(aka broadcast or fragment replicate join) when
> possible. we need to research how to make it workable with Hive on Spark.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
