sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1279) Sqoop connection resiliency option breaks older Mysql versions that don't have JDBC 4 methods
Date Fri, 07 Feb 2014 03:05:19 GMT

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

Hudson commented on SQOOP-1279:
-------------------------------

SUCCESS: Integrated in Sqoop-ant-jdk-1.6-hadoop200 #882 (See [https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop200/882/])
SQOOP-1279. Sqoop connection resiliency option breaks older Mysql versions that don't have
JDBC 4 methods (hshreedharan: https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=c913f77f284cb27ce5aa43fd433b59a52d3032b3)
* src/java/org/apache/sqoop/mapreduce/db/DBRecordReader.java


> 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)

Mime
View raw message