You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2013/03/07 17:30:14 UTC
[jira] [Assigned] (SQOOP-933) Properly log SQLExceptions using
getNextException() method for chaining exceptions
[ https://issues.apache.org/jira/browse/SQOOP-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Jarcec Cecho reassigned SQOOP-933:
----------------------------------------
Assignee: Jarek Jarcec Cecho
> Properly log SQLExceptions using getNextException() method for chaining exceptions
> ----------------------------------------------------------------------------------
>
> Key: SQOOP-933
> URL: https://issues.apache.org/jira/browse/SQOOP-933
> Project: Sqoop
> Issue Type: Improvement
> Affects Versions: 1.4.2
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.4.4
>
> Attachments: bugSQOOP-933.patch
>
>
> We're not using the [SQLException::getNextException|http://docs.oracle.com/javase/6/docs/api/java/sql/SQLException.html#getNextException()] in Sqoop code base, however some of the JDBC drivers do and we're not correctly logging their exceptions. I think that we should improve that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira