sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2787) MySql import and export fails with 5.1 server and 5.1.17+ drivers
Date Sat, 20 Feb 2016 06:44:18 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155431#comment-15155431
] 

ASF subversion and git services commented on SQOOP-2787:
--------------------------------------------------------

Commit b84ebf1e8475946dad2e9e2a83d58280d715ef1c in sqoop's branch refs/heads/trunk from [~venkatnrangan]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=b84ebf1 ]

SQOOP-2787: MySql import and export fails with 5.1 server and 5.1.17+ drivers
    (Sowmya Ramesh via Venkat Ranganathan)


> MySql import and export fails with 5.1 server and 5.1.17+ drivers 
> ------------------------------------------------------------------
>
>                 Key: SQOOP-2787
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2787
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.6
>         Environment: MySql 5.1.x server and 5.1.17+ driver
>            Reporter: Venkat Ranganathan
>            Assignee: Sowmya Ramesh
>             Fix For: 1.4.7
>
>         Attachments: SQOOP-2787.V0.patch, SQOOP-2787.V1.patch
>
>
> As discussed in SQOOP-1400 and SQOOP-1617,  there are combinations and versions of MySQL
server and driver that cause the import and export to fail when the metadata of the tables
are being fetched.
> {quote}
> 16/01/07 21:48:14 DEBUG manager.SqlManager: No connection paramenters specified. Using
regular API for making connection.
> 16/01/07 21:48:14 DEBUG manager.SqlManager: Using fetchSize for next query: -2147483648
> 16/01/07 21:48:14 INFO manager.SqlManager: Executing SQL statement: SELECT t.* FROM `t1`
AS t LIMIT 1
> 16/01/07 21:48:14 DEBUG manager.SqlManager: Found column col1 of type 4, 11, 0
> 16/01/07 21:48:14 ERROR manager.SqlManager: Error reading from database: java.sql.SQLException:
Streaming result set com.mysql.jdbc.RowDataDynamic@17980bdc is still active. No statements
may be issued when any streaming result sets are open and in use on a given connection. Ensure
that you have called .close() on any active streaming result sets before attempting more queries.
> java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@17980bdc is
still active. No statements may be issued when any streaming result sets are open and in use
on a given connection. Ensure that you have called .close() on any active streaming result
sets before attempting more queries.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:934)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:931)
> at com.mysql.jdbc.MysqlIO.checkForOutstandingStreamingData(MysqlIO.java:2735)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1899)
> {quote}
> One potential solution for imports is to add the fetch-size parameter with a valid value
to satisfy some of the scenarios when incompatible server/driver versions are used if upgrading
either the server or driver is not feasible
> Such a workaround is not possible with exports as export operations do not honor the
fetch size option.    One potential solution for exports is to explicitly set the fetch size
for exports to 0 in MySQLManager  so that this issue is addressed for exports.   Fetching
entire result set into memory and OOM issues will not be a factor as we are dealing only with
metadata



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

Mime
View raw message