[
https://issues.apache.org/jira/browse/SQOOP-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894143#comment-13894143
]
ASF subversion and git services commented on SQOOP-1279:
--------------------------------------------------------
Commit c913f77f284cb27ce5aa43fd433b59a52d3032b3 in branch refs/heads/trunk from
[~hshreedharan]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=c913f77 ]
SQOOP-1279. Sqoop connection resiliency option breaks older Mysql versions that
don't have JDBC 4 methods
(Venkat Ranganathan via Hari Shreedharan)
> 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)
