[
https://issues.apache.org/jira/browse/SQOOP-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008488#comment-14008488
]
Hudson commented on SQOOP-1320:
-------------------------------
SUCCESS: Integrated in Sqoop2-hadoop100 #601 (See
[https://builds.apache.org/job/Sqoop2-hadoop100/601/])
SQOOP-1320. Sqoop2: Log entire SQLExceptions chain in GenericJdbcExecutor
(hshreedharan:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=0756d13662913a7c2df1a0a4d23cd50175dc42f4)
*
connector/connector-generic-jdbc/src/main/java/org/apache/sqoop/connector/jdbc/GenericJdbcExecutor.java
> Log entire SQLExceptions chain in GenericJdbcExecutor
> -----------------------------------------------------
>
> Key: SQOOP-1320
> URL: https://issues.apache.org/jira/browse/SQOOP-1320
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.3
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.4
>
> Attachments: SQOOP-1320.patch
>
>
> I've noticed that current {{GenericJdbcExecutor}} class won't print out
> exceptions that are hidden in {{getNextException()}} method call. As this
> chaining is still used by various JDBC drivers, we need to tweak the executor
> to print them out.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
