sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bilung Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-314) Basic export hangs when target database does not support INSERT syntax with multiple rows of values
Date Fri, 12 Aug 2011 16:52:27 GMT

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

Bilung Lee updated SQOOP-314:
-----------------------------

    Description: 
Basic export job will hang when the target database does not support INSERT syntax with multiple
rows of values, such as INSERT INTO tbl (col1, col2) VALUES(11, 12),(21, 22),(23, 24)

This is because, in close(), AsyncSqlRecordWriter will still wait for AsyncSqlExecThread to
finish even when an SQLException is thrown underneath.

The configuration variable "sqoop.export.records.per.statement" can be set to 1 as a workaround
for this problem.

  was:
Basic export job will hang when the target database does not support INSERT syntax with multiple
rows of values, such as INSERT INTO tbl (col1, col2) VALUES(11, 12),(21, 22),(23, 24)

This is because, in close(), AsyncSqlRecordWriter will still wait for AsyncSqlExecThread to
finish even when an SQLException is thrown underneath.

The configuration variable "sqoop.connection.factories" can be set to 1 as a workaround for
this problem.


> Basic export hangs when target database does not support INSERT syntax with multiple
rows of values
> ---------------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-314
>                 URL: https://issues.apache.org/jira/browse/SQOOP-314
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Bilung Lee
>            Priority: Minor
>
> Basic export job will hang when the target database does not support INSERT syntax with
multiple rows of values, such as INSERT INTO tbl (col1, col2) VALUES(11, 12),(21, 22),(23,
24)
> This is because, in close(), AsyncSqlRecordWriter will still wait for AsyncSqlExecThread
to finish even when an SQLException is thrown underneath.
> The configuration variable "sqoop.export.records.per.statement" can be set to 1 as a
workaround for this problem.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message