[
https://issues.apache.org/jira/browse/SQOOP-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248634#comment-14248634
]
Veena Basavaraj commented on SQOOP-1879:
----------------------------------------
even without my patch the version test fails.:)
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.sqoop.integration.connector.jdbc.generic.FromHDFSToRDBMSTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.184 sec
Running org.apache.sqoop.integration.connector.jdbc.generic.FromRDBMSToHDFSTest
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 22.747 sec <<<
FAILURE!
Running org.apache.sqoop.integration.connector.jdbc.generic.PartitionerTest
Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 196.126 sec
Running org.apache.sqoop.integration.connector.jdbc.generic.TableStagedRDBMSTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.484 sec
Running org.apache.sqoop.integration.connector.kafka.FromRDBMSToKafkaTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.754 sec
Running
org.apache.sqoop.integration.repository.derby.upgrade.Derby1_99_4UpgradeTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 121.856 sec <<<
FAILURE!
Running
org.apache.sqoop.integration.server.SubmissionWithDisabledModelObjectsTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.672 sec
Running org.apache.sqoop.integration.server.VersionTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.297 sec <<<
FAILURE!
Results :
Failed tests:
testColumns(org.apache.sqoop.integration.connector.jdbc.generic.FromRDBMSToHDFSTest)
testVersion(org.apache.sqoop.integration.server.VersionTest): expected:<[Tue
Dec 16 08:38:31] PST 2014> but was:<[Sat Dec 13 18:20:35] PST 2014>
Tests in error:
testPostUpgrade(org.apache.sqoop.integration.repository.derby.upgrade.Derby1_99_4UpgradeTest):
Failed to start the Tomcat 6.x container. Check the
[/Users/vbasavaraj/Projects/sqoop2/test/target/sqoop-cargo-tests/org.apache.sqoop.integration.repository.derby.upgrade.Derby1_99_4UpgradeTest/testPostUpgrade/sqoop-mini-cluster//log/tomcat.log]
file containing the container logs for more details.
Tests run: 30, Failures: 2, Errors: 1, Skipped: 0
> Sqoop2: Submission Engine does not set all details on SubmissionRecord in
> Local mode
> ------------------------------------------------------------------------------------
>
> Key: SQOOP-1879
> URL: https://issues.apache.org/jira/browse/SQOOP-1879
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Attachments: SQOOP-1879-v1.patch, SQOOP-1879-v2.patch,
> SQOOP-1879-v4.patch, SQOOP-1879-v5.patch
>
>
> {code}
> // If we're in local mode than wait on completion. Local job runner do
> not
> // seems to be exposing API to get previously submitted job which makes
> // other methods of the submission engine quite useless.
> if(isLocal()) {
> job.waitForCompletion(true);
> } else {
> job.submit();
> }
> {code}
> the above code says that the job.waitForCompletion(true) is blocking and
> hence the other submisison engine apis are useless in this local mode.
> But we dont set the all attributes of the job run into the submission record
> in this case
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
