You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Szabolcs Vasas (JIRA)" <ji...@apache.org> on 2018/06/20 11:16:00 UTC

[jira] [Resolved] (SQOOP-3333) Change default behavior of the MS SQL connector to non-resilient.

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

Szabolcs Vasas resolved SQOOP-3333.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0

Hi [~fero],

Thank you for your contribution, you can close your review request now.

Szabolcs

> Change default behavior of the MS SQL connector to non-resilient.
> -----------------------------------------------------------------
>
>                 Key: SQOOP-3333
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3333
>             Project: Sqoop
>          Issue Type: Task
>            Reporter: Fero Szabo
>            Assignee: Fero Szabo
>            Priority: Major
>             Fix For: 3.0.0
>
>
> The default behavior of Sqoop is to use a "resilient" retry mechanism in the SQL Server connector. However, this relies on the split-by column being unique and ordered ascending. This can lead to obscure errors (duplicate or missing records in imports / exports) and should be used only if specifically wanted by the users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)