Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <2920288.460891285759653299.JavaMail.jira@thor>
Date: Wed, 29 Sep 2010 07:27:33 -0400 (EDT)
From: "Yuanjun Li (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Commented: (HIVE-1524) parallel execution failed if
 mapred.job.name is set
In-Reply-To: <22868800.249041281421997142.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-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916108#action_12916108 ] 

Yuanjun Li commented on HIVE-1524:
----------------------------------

I have done the load test in our company using branch 0.6 with HIVE-1524 patch, it seems ok. 
And another interesting thing is the HIVE-1019 problem will be sloved by HIVE-1524 as same time, if HIVE-1524 works well with branch 0.6

> parallel execution failed if mapred.job.name is set
> ---------------------------------------------------
>
>                 Key: HIVE-1524
>                 URL: https://issues.apache.org/jira/browse/HIVE-1524
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.5.0
>            Reporter: Ning Zhang
>            Assignee: Ning Zhang
>             Fix For: 0.6.0, 0.7.0
>
>         Attachments: HIVE-1524-for-Hive-0.6.patch, HIVE-1524.2.patch, HIVE-1524.patch
>
>
> The plan file name was generated based on mapred.job.name. If the user specify mapred.job.name before the query, two parallel queries will have conflict plan file name. 

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