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] [Commented] (SQOOP-1107) Further improve error reporting when exporting malformed data
Date Mon, 02 Sep 2013 07:43:53 GMT

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

Jarek Jarcec Cecho commented on SQOOP-1107:

The failure in profile 200 is a jenkins issue.
> Further improve error reporting when exporting malformed data
> -------------------------------------------------------------
>                 Key: SQOOP-1107
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1107
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.3
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>            Priority: Trivial
>             Fix For: 1.4.5
>         Attachments: bugSQOOP-1107.patch
> We've significantly improved error handling when exporting malformed data in SQOOP-720,
where we started dumping a lot of state into log. Unfortunately current output do show on
which column the parsing exception occurred. This is usually not an issue for primitive Java
types as the underlying exception is descriptive enough:
> {code}
> Caused by: java.lang.NumberFormatException: For input string: "A"
> 	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> 	at java.lang.Integer.parseInt(Integer.java:449)
> 	at java.lang.Integer.valueOf(Integer.java:554)
> 	at text.__loadFromFields(text.java:196)
> {code}
> However {{BigDecimal}} do not print out the value:
> {code}
> Exception: 
> java.lang.NumberFormatException
> 	at java.math.BigDecimal.<init>(BigDecimal.java:459)
> 	at java.math.BigDecimal.<init>(BigDecimal.java:728)
> {code}
> I would therefore suggest to start catching {{RuntimeException}}s in the parsing code
and re-throwing them with value of currently parsed column.

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

View raw message