[
https://issues.apache.org/jira/browse/SQOOP-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054050#comment-15054050
]
ASF subversion and git services commented on SQOOP-2712:
--------------------------------------------------------
Commit e077f9978343a68833e16e0fb044a687fa208aad in sqoop's branch
refs/heads/trunk from [~kathleen]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=e077f99 ]
SQOOP-2712: Run only one map task attempt during export (second edition)
(Jarek Jarcec Cecho via Kate Ting)
> 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)
