sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bilung Lee (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-357) To make debugging easier, Sqoop should print out all the exceptions
Date Fri, 07 Oct 2011 18:36:29 GMT

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

Bilung Lee updated SQOOP-357:
-----------------------------

    Attachment: SQOOP-357-1.patch
    
> 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
>         Attachments: SQOOP-357-1.patch, SQOOP-357.patch
>
>
> 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

        

Mime
View raw message