Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <722174223.128801262981994750.JavaMail.jira@brutus.apache.org>
Date: Fri, 8 Jan 2010 20:19:54 +0000 (UTC)
From: "He Yongqiang (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Updated: (HIVE-964) handle skewed keys for a join in a
 separate job
In-Reply-To: <1912961816.1259719640746.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

He Yongqiang updated HIVE-964:
------------------------------

    Attachment: hive-964-2010-01-08.patch

CHANGES:
1) let row container use hadoop fileformat
2) let row container directly upload file to dfs
3) added logic to handle reducer failure (we should not see results of a failure reducer) .
4) write one file per skew key and combinefileinputformat.

> handle skewed keys for a join in a separate job
> -----------------------------------------------
>
>                 Key: HIVE-964
>                 URL: https://issues.apache.org/jira/browse/HIVE-964
>             Project: Hadoop Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Namit Jain
>            Assignee: He Yongqiang
>         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
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.