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/01/03 07:18:12 UTC

[jira] [Commented] (SQOOP-808) SQLExceptions From Batched Exports Aren't Very Helpful

    [ https://issues.apache.org/jira/browse/SQOOP-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542740#comment-13542740 ] 

Jarek Jarcec Cecho commented on SQOOP-808:
------------------------------------------

Hi Nick,
I'm wondering, my logs seems to always contain entire exception chain, so why not simply look at next exception? I'm worried about silently skipping top level exception as it might hide issues and actually might fail in case that getNextException() will be null.

Jarcec
                
> SQLExceptions From Batched Exports Aren't Very Helpful
> ------------------------------------------------------
>
>                 Key: SQOOP-808
>                 URL: https://issues.apache.org/jira/browse/SQOOP-808
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.2
>            Reporter: Nick White
>             Fix For: 1.4.3
>
>         Attachments: SQOOP-808.patch
>
>
> They just show the error messages from the BatchUpdateException, which has a generic message saying look at the result of getNextException() for specific details.

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