[
https://issues.apache.org/jira/browse/SQOOP-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122916#comment-13122916
]
[email protected] commented on SQOOP-357:
-----------------------------------------------------
bq. On 2011-10-07 02:41:42, Arvind Prabhakar wrote:
bq. > Overall the changes look good. One suggestion though - would it be
possible to move the logging logic for SQLException in a Util class somewhere
(perhaps a new util class called ExceptionUtils in org.apache.sqoop). That way,
in other places where we catch SQLException, we could simply invoke this method.
Thanks for your feedback! A utility class is added in new patch.
- Bilung
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2265/#review2424
-----------------------------------------------------------
On 2011-10-07 02:15:04, Bilung Lee wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2265/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-10-07 02:15:04)
bq.
bq.
bq. Review request for Sqoop and Arvind Prabhakar.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Currently, only the error message of the first exception in a chain will
be logged.
bq. However, the root cause exception may be buried in the exception chain.
bq. To help diagnose the root cause, we need to log all error messages in the
chain.
bq.
bq.
bq. This addresses bug SQOOP-357.
bq. https://issues.apache.org/jira/browse/SQOOP-357
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. ./src/java/com/cloudera/sqoop/mapreduce/AsyncSqlRecordWriter.java
1179036
bq. ./src/java/com/cloudera/sqoop/mapreduce/db/DBRecordReader.java 1179036
bq.
bq. Diff: https://reviews.apache.org/r/2265/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq.
bq. Thanks,
bq.
bq. Bilung
bq.
bq.
> To make debugging easier, Sqoop should print out all the exceptions
> --------------------------------------------------------------------
>
> Key: SQOOP-357
> URL: https://issues.apache.org/jira/browse/SQOOP-357
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Prashant Gokhale
> Assignee: Bilung Lee
>
> I am using sqoop version from https://github.com/apache/sqoop (trunk) . I am
> pasting some of the error message lines I get when I try to run an import
> command
> SELECT ID, FIRSTNAME, LASTNAME FROM TEST_TABLE AS TEST_TABLE WHERE ( ID >= 10
> ) AND ( ID < 15 ). Details of the failure can be found in the exception chain
> that is accessible with getNextException.
> .....
> at
> com.cloudera.sqoop.mapreduce.db.DBRecordReader.executeQuery(DBRecordReader.java:110)
> at
> com.cloudera.sqoop.mapreduce.db.DBRecordReader.nextKeyValue(DBRecordReader.java:235)
> ... 11 more
> It does not print out the entire list of exceptions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
