You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Xuefu Zhang (JIRA)" <ji...@apache.org> on 2014/12/01 04:35:14 UTC
[jira] [Commented] (HIVE-8943) Fix memory limit check for combine
nested mapjoins [Spark Branch]
[ https://issues.apache.org/jira/browse/HIVE-8943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229387#comment-14229387 ]
Xuefu Zhang commented on HIVE-8943:
-----------------------------------
Thanks, Szehon! I'm reviewing it now.
> Fix memory limit check for combine nested mapjoins [Spark Branch]
> -----------------------------------------------------------------
>
> Key: HIVE-8943
> URL: https://issues.apache.org/jira/browse/HIVE-8943
> Project: Hive
> Issue Type: Sub-task
> Components: Spark
> Affects Versions: spark-branch
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Attachments: HIVE-8943.1-spark.patch, HIVE-8943.1-spark.patch, HIVE-8943.2-spark.patch, HIVE-8943.3-spark.patch
>
>
> Its the opposite problem of what we thought in HIVE-8701.
> SparkMapJoinOptimizer does combine nested mapjoins into one work due to removal of RS for big-table. So we need to enhance the check to calculate if all the MapJoins in that work (spark-stage) will fit into the memory, otherwise it might overwhelm memory for that particular spark executor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)