[SQOOP-3133] Sqoop (export + --non-resilient) with SQLServer ignores Sqoop option (-Dsqoop.export.statements.per.transaction)

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: docs
• Assignee: Unassigned
• Reporter: Markus Kemper
• Created: 13/Feb/17 19:42
• Updated: 06/Jun/18 14:15

Description

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.

Issue Links

• is related to: SQOOP-3332 Extend Documentation of --resilient flag and add warning message when detected