[
https://issues.apache.org/jira/browse/SQOOP-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajkumar updated SQOOP-2886:
----------------------------
Environment: Hadoop 2.6.0, SQL Server 2008 R2, Sqoop 1.4.6 (was: Hadoop
2.6.0, SQL Server 2008 R2)
Priority: Critical (was: Major)
Description:
Sqoop export job to SQL Server works well with anything less number of
columns(less than 15). If 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?
was:
Sqoop export job to SQL Server works well with anything less than 13 columns.
If 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?
> 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
> Priority: Critical
>
> Sqoop export job to SQL Server works well with anything less number of
> columns(less than 15). If 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)
