[
https://issues.apache.org/jira/browse/SQOOP-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994783#comment-13994783
]
Hari Shreedharan commented on SQOOP-1320:
-----------------------------------------
+1. I am not entirely sure recursing within the logSQLException method is a
good idea - but since the chain is likely to be small, I guess it is ok for now.
> 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)
