sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajkumar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-2886) Sqoop export to SQL Server fails/hangs for more number of columns
Date Thu, 17 Mar 2016 18:52:33 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajkumar updated SQOOP-2886:
----------------------------
    Description: 
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?

  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. 

I guess this problem only exists with 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
>            Reporter: Rajkumar
>
> 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?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message