[
https://issues.apache.org/jira/browse/SQOOP-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544792#comment-13544792
]
Jarek Jarcec Cecho commented on SQOOP-808:
------------------------------------------
Hi Nick,
thank you very much for your examples. They indeed helped me understand your
issue. I've google around and I did not found better solution.
Before I'll commit your patch - would you mind cleaning up check style warnings
(you can run check style report by "ant checkstyle") and appending comment why
you're looking into the next exception (maybe linking this issue?)?
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.1.patch, SQOOP-808.patch,
> TestSQLErrorMessages.java, TestSQLErrorMessages.log
>
>
> 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
