sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-1279) Sqoop connection resiliency option breaks older Mysql versions that don't have JDBC 4 methods
Date Tue, 06 May 2014 02:27:15 GMT

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

Jarek Jarcec Cecho updated SQOOP-1279:
--------------------------------------

    Fix Version/s: 1.4.5

> 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
>             Fix For: 1.4.5
>
>         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.2#6252)

Mime
View raw message