You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "VISHNU S NAIR (JIRA)" <ji...@apache.org> on 2016/03/22 09:56:25 UTC
[jira] [Assigned] (SQOOP-2886) Sqoop export to SQL Server
fails/hangs for more number of columns
[ https://issues.apache.org/jira/browse/SQOOP-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
VISHNU S NAIR reassigned SQOOP-2886:
------------------------------------
Assignee: VISHNU S NAIR
> Sqoop export to SQL Server fails/hangs for more number of columns
> ------------------------------------------------------------------
>
> Key: SQOOP-2886
> URL: https://issues.apache.org/jira/browse/SQOOP-2886
> Project: Sqoop
> Issue Type: Bug
> Components: connectors/sqlserver
> Affects Versions: 1.4.6
> Environment: Hadoop 2.6.0, SQL Server 2008 R2, Sqoop 1.4.6
> Reporter: Rajkumar
> Assignee: VISHNU S NAIR
> Priority: Critical
>
> Sqoop export job to SQL Server works well with few number of columns(anything less than 15). When the number of column increases the mapreduce job hangs at 100%.
> Additionally, I tested the same scenario with MySQL db and the jobs were successfully exporting records for any number of columns.
> Looks like this problem occurs only when exporting data to SQL Server. Can anyone please provide a workaround until we get a fix for this issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)