CODEWITHSUNDEEP
hadooptransactionssqoopazure-synapse
rh979
rh979

Reputation: 667

Changing Transaction Isolation level setting behavior in Sqoop

We are currently trying to use Sqoop to ingest data from Hadoop to Azure SQL Data Warehouse but getting error related to Transaction isolation level. What's happening is that Sqoop tries to set transaction isolation level to READ COMMITTED while trying to import/export whereas this feature isn't currently supported in Azure SQL Data warehouse. I've tried using --relaxed-isolation parameter of Sqoop but still no effect. As a solution, I am thinking to: 1. Change Sqoop source code to alter Sqoop's behavior to not set transaction level 2. Look for APIs (if any) that may allow me to change this Sqoop's behavior programmatically.

Has anyone encountered such scenario? Looking for suggestions for the proposed solutions and how to go about them.

Upvotes: 1

Views: 1521

Answers (1)

Alexandre Gattiker
Alexandre Gattiker

Reputation: 749

This issue has just been resolved in Sqoop: https://issues.apache.org/jira/browse/SQOOP-2349

Otherwise, @wBob's comment about using Polybase is definitely best practice: https://learn.microsoft.com/en-us/azure/data-factory/data-factory-azure-sql-data-warehouse-connector#use-polybase-to-load-data-into-azure-sql-data-warehouse

Upvotes: 3

Related Questions