You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Venkat Ranganathan (JIRA)" <ji...@apache.org> on 2014/02/06 21:56:22 UTC

[jira] [Updated] (SQOOP-1279) Sqoop connection resiliency option breaks older Mysql versions that don't have JDBC 4 methods

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

Venkat Ranganathan updated SQOOP-1279:
--------------------------------------

    Attachment: SQOOP-1279.patch

> Sqoop connection resiliency option breaks older Mysql versions that don't have JDBC 4 methods
> ---------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-1279
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1279
>             Project: Sqoop
>          Issue Type: Bug
>         Environment: Mysql 5.0.8 connector/J
>            Reporter: Venkat Ranganathan
>            Assignee: Venkat Ranganathan
>            Priority: Critical
>         Attachments: SQOOP-1279.patch
>
>
> The connection resiliency changes (SQOOP-1056 and SQOOP-1057) add additional checks on the preparedStatement (Statement.isClosed())  that is introduced in JDBC 4 as part of JDK 6.   That method is not available in older drivers that are not JDBC4 compliant.   Since this is a backward breaking change proposing to fix it.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)