You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Markus Kemper (JIRA)" <ji...@apache.org> on 2017/02/13 19:42:41 UTC
[jira] [Created] (SQOOP-3133) Sqoop (export + --non-resilient) with
SQLServer ignores Sqoop option (-Dsqoop.export.statements.per.transaction)
Markus Kemper created SQOOP-3133:
------------------------------------
Summary: Sqoop (export + --non-resilient) with SQLServer ignores Sqoop option (-Dsqoop.export.statements.per.transaction)
Key: SQOOP-3133
URL: https://issues.apache.org/jira/browse/SQOOP-3133
Project: Sqoop
Issue Type: Bug
Components: docs
Reporter: Markus Kemper
Please consider updating the doc to clarify this limitation.
When using Sqoop (export + --non-resilient) with SQLServer it ignores Sqoop option (-Dsqoop.export.statements.per.transaction) which means that each export task will execute within a single RDBMS transaction instead of committing on interval as it proceeds.
This could be considered a desirable behavior for rolling back a failure during export however it may not be ideal for performance.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)