Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Message-ID: <18215596.71191288057462920.JavaMail.jira@thor>
Date: Mon, 25 Oct 2010 21:44:22 -0400 (EDT)
From: "Namit Jain (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Commented: (HIVE-1641) add map joined table to distributed
 cache
In-Reply-To: <13590686.214051284588097173.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Namit Jain commented on HIVE-1641:
----------------------------------

Let us try to get it in, there are some other big patches waiting and it will be difficult for you to maintain this

> add map joined table to distributed cache
> -----------------------------------------
>
>                 Key: HIVE-1641
>                 URL: https://issues.apache.org/jira/browse/HIVE-1641
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>    Affects Versions: 0.7.0
>            Reporter: Namit Jain
>            Assignee: Liyin Tang
>             Fix For: 0.7.0
>
>         Attachments: Hive-1641(3).txt, Hive-1641(4).patch, Hive-1641(5).patch, Hive-1641.patch
>
>
> Currently, the mappers directly read the map-joined table from HDFS, which makes it difficult to scale.
> We end up getting lots of timeouts once the number of mappers are beyond a few thousand, due to 
> concurrent mappers.
> It would be good idea to put the mapped file into distributed cache and read from there instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.