You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2014/11/08 17:11:34 UTC

[jira] [Updated] (SQOOP-1320) Sqoop2: Log entire SQLExceptions chain in GenericJdbcExecutor

     [ https://issues.apache.org/jira/browse/SQOOP-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gwen Shapira updated SQOOP-1320:
--------------------------------
    Summary: Sqoop2: Log entire SQLExceptions chain in GenericJdbcExecutor  (was: Log entire SQLExceptions chain in GenericJdbcExecutor)

> Sqoop2: 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.3.4#6332)