sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-2712) Run only one map task attempt during export (second edition)
Date Tue, 24 Nov 2015 17:47:11 GMT

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

Jarek Jarcec Cecho updated SQOOP-2712:
--------------------------------------
    Attachment: SQOOP-2712.patch

Attaching simple patch, so skipping review board.

> Run only one map task attempt during export (second edition)
> ------------------------------------------------------------
>
>                 Key: SQOOP-2712
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2712
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.6
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.4.7
>
>         Attachments: SQOOP-2712.patch
>
>
> In SQOOP-2055 I've provided facility to not run multiple map task attempts by default
in export case as that doesn't make sense in most scenarios. However looking closely into
the patch, it seems that I did a small typo:
> {code}
>     int sqoopMaxAttempts = conf.getInt(SQOOP_EXPORT_MAP_TASK_MAX_ATTEMTPS, 1);
>     if (sqoopMaxAttempts > 1) {
>       conf.setInt(HADOOP_MAP_TASK_MAX_ATTEMTPS, sqoopMaxAttempts);
>     }
> {code}
> Since {{SQOOP_EXPORT_MAP_TASK_MAX_ATTEMTPS}} is 1 by default, the {{if}} statement won't
be called at all and hence we won't limit the number of attempts to 1 as expected. We should
fix the condition to {{sqoopMaxAttempts >0}} instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message