[
https://issues.apache.org/jira/browse/SQOOP-3333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518033#comment-16518033
]
Hudson commented on SQOOP-3333:
-------------------------------
SUCCESS: Integrated in Jenkins build Sqoop-hadoop200 #1175 (See
[https://builds.apache.org/job/Sqoop-hadoop200/1175/])
SQOOP-3333: Change default behavior of the MS SQL connector to (vasas:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=57278b9e3370dc65cb465e9ed3cb225203dc7eab])
* (edit)
src/test/org/apache/sqoop/manager/sqlserver/SQLServerManagerImportTest.java
* (add)
src/test/org/apache/sqoop/manager/sqlserver/TestSqlServerManagerContextConfigurator.java
* (edit) src/docs/user/connectors.txt
* (edit) src/java/org/apache/sqoop/manager/ExportJobContext.java
* (edit) src/java/org/apache/sqoop/manager/SQLServerManager.java
* (add)
src/java/org/apache/sqoop/manager/SqlServerManagerContextConfigurator.java
> 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
>
> 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)
