sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-1320) Log entire SQLExceptions chain in GenericJdbcExecutor
Date Sun, 11 May 2014 22:38:14 GMT

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

Jarek Jarcec Cecho updated SQOOP-1320:
--------------------------------------

    Attachment: SQOOP-1320.patch

Relatively simple patch that just adds bunch of print calls, so I'm skipping review board.
I've verified the exception traces on real cluster with real issue.

> 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)

Mime
View raw message