[
https://issues.apache.org/jira/browse/SQOOP-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233481#comment-14233481
]
Veena Basavaraj commented on SQOOP-1837:
----------------------------------------
I tried this patch for my SQOOP-1815 use case.
No luck. the exception Info is null. There is some place else that it is
swallowing the real issue underneath the 1815 use case
{code}
....
String jobId = job.getJobID().toString();
request.getSummary().setExternalId(jobId);
request.getSummary().setExternalLink(job.getTrackingURL());
LOG.debug("Executed new map-reduce job with id " + jobId);
} catch (Exception e) {
request.getSummary().setException(e);
LOG.error("Error in submitting job", e);
return false;
}
return true;
}
{code}
> Sqoop2: Verify that executing job has been successful in ConnectorTestCase
> --------------------------------------------------------------------------
>
> Key: SQOOP-1837
> URL: https://issues.apache.org/jira/browse/SQOOP-1837
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.4
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.5
>
> Attachments: SQOOP-1837.patch
>
>
> While investigating SQOOP-1815 we've spent a lot of time with [~vybs] trying
> to see why we are not getting data that we are expecting. We finally realized
> that the submission itself is failing and that is why we don't see any data.
> It seems that our [util
> classes|https://github.com/apache/sqoop/blob/sqoop2/test/src/main/java/org/apache/sqoop/test/testcases/ConnectorTestCase.java#L244]
> for executing job are running the job without checking whether it was
> successful or not. Hence the test didn't noticed that the job failed and move
> to the stage for checking job outputs that haven't been there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
