Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <645809961.234541265991808088.JavaMail.jira@brutus.apache.org>
Date: Fri, 12 Feb 2010 16:23:28 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1469) Sqoop should disable speculative
 execution in export
In-Reply-To: <1266647322.138151265679207979.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833052#action_12833052 ] 

Hudson commented on MAPREDUCE-1469:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #233 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/233/])
    . Sqoop should disable speculative execution in export. Contributed by Aaron Kimball.


> Sqoop should disable speculative execution in export
> ----------------------------------------------------
>
>                 Key: MAPREDUCE-1469
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1469
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/sqoop
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>             Fix For: 0.22.0
>
>         Attachments: MAPREDUCE-1469.patch
>
>
> Concurrent writers of the same output shard may cause the database to try to insert duplicate primary keys concurrently. Not a good situation. Speculative execution should be forced off for this operation.

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