[
https://issues.apache.org/jira/browse/HIVE-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14480862#comment-14480862
]
Alexander Pivovarov commented on HIVE-964:
------------------------------------------
The fix adds new field to JoinDesc.java
private tableDesc keyTableDesc;
https://github.com/apache/hive/commit/e4f997f52bb79012d9d94bd6105e86ebea3e29cf
MapJoinDesc which extends JoinDesc already had similar field
private tableDesc keyTblDesc;
https://github.com/apache/hive/blob/e4f997f52bb79012d9d94bd6105e86ebea3e29cf/ql/src/java/org/apache/hadoop/hive/ql/plan/mapJoinDesc.java
(line 42)
should MapJoinDesc use parent get/set KeyTableDesc() instead of having its own
keyTblDesc field?
> handle skewed keys for a join in a separate job
> -----------------------------------------------
>
> Key: HIVE-964
> URL: https://issues.apache.org/jira/browse/HIVE-964
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: He Yongqiang
> Fix For: 0.6.0
>
> Attachments: hive-964-2009-12-17.txt, hive-964-2009-12-28-2.patch,
> hive-964-2009-12-29-4.patch, hive-964-2010-01-08.patch,
> hive-964-2010-01-13-2.patch, hive-964-2010-01-14-3.patch,
> hive-964-2010-01-15-4.patch
>
>
> The skewed keys can be written to a temporary table or file, and a followup
> conditional task can be used to perform the join on those keys.
> As a first step, JDBM can be used for those keys
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
