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

Sqoop QA bot commented on SQOOP-2539:
-------------------------------------

Testing file 
[SQOOP-2539.005.patch|https://issues.apache.org/jira/secure/attachment/12754616/SQOOP-2539.005.patch]
 against branch sqoop2 took 0:00:07.877268.

{color:red}Overall:{color} -1 due to an error(s), see details below:

{color:green}SUCCESS:{color} Clean was successful
{color:red}ERROR:{color} Failed to apply patch (exit code 1):
{code}error: patch failed: 
repository/repository-common/src/main/java/org/apache/sqoop/repository/common/CommonRepoUtils.java:27
error: 
repository/repository-common/src/main/java/org/apache/sqoop/repository/common/CommonRepoUtils.java:
 patch does not apply
error: patch failed: 
repository/repository-derby/src/main/java/org/apache/sqoop/repository/derby/DerbyRepositoryHandler.java:312
error: 
repository/repository-derby/src/main/java/org/apache/sqoop/repository/derby/DerbyRepositoryHandler.java:
 patch does not apply
error: patch failed: 
repository/repository-derby/src/main/java/org/apache/sqoop/repository/derby/DerbySchemaUpgradeQuery.java:633
error: 
repository/repository-derby/src/main/java/org/apache/sqoop/repository/derby/DerbySchemaUpgradeQuery.java:
 patch does not apply
error: patch failed: 
repository/repository-mysql/src/main/java/org/apache/sqoop/repository/mysql/MySqlSchemaCreateQuery.java:42
error: 
repository/repository-mysql/src/main/java/org/apache/sqoop/repository/mysql/MySqlSchemaCreateQuery.java:
 patch does not apply
error: patch failed: 
repository/repository-postgresql/src/main/java/org/apache/sqoop/repository/postgresql/PostgresqlRepositoryHandler.java:139
error: 
repository/repository-postgresql/src/main/java/org/apache/sqoop/repository/postgresql/PostgresqlRepositoryHandler.java:
 patch does not apply
error: 
repository/repository-postgresql/src/main/java/org/apache/sqoop/repository/postgresql/PostgresqlSchemaUpgradeQuery.java:
 already exists in working directory
error: patch failed: 
shell/src/main/java/org/apache/sqoop/shell/utils/ConfigFiller.java:888
error: shell/src/main/java/org/apache/sqoop/shell/utils/ConfigFiller.java: 
patch does not apply
error: patch failed: 
test/src/main/java/org/apache/sqoop/test/infrastructure/SqoopTestCase.java:40
error: 
test/src/main/java/org/apache/sqoop/test/infrastructure/SqoopTestCase.java: 
patch does not apply
error: patch failed: 
test/src/main/java/org/apache/sqoop/test/testcases/ConnectorTestCase.java:36
error: 
test/src/main/java/org/apache/sqoop/test/testcases/ConnectorTestCase.java: 
patch does not apply
error: test/src/main/java/org/apache/sqoop/test/utils/SqoopUtils.java: already 
exists in working directory
error: 
test/src/test/java/org/apache/sqoop/integration/repository/derby/upgrade/Derby1_99_5UpgradeTest.java:
 already exists in working directory
error: 
test/src/test/java/org/apache/sqoop/integration/repository/derby/upgrade/Derby1_99_6UpgradeTest.java:
 already exists in working directory
error: test/src/test/resources/repository/derby/derby-repository-1.99.5.tar.gz: 
already exists in working directory
error: test/src/test/resources/repository/derby/derby-repository-1.99.6.tar.gz: 
already exists in working directory
{code}


Console output is available 
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1672/console].

This message is automatically generated.

> Sqoop2: Enforce resource name not null when creating table
> ----------------------------------------------------------
>
>                 Key: SQOOP-2539
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2539
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Dian Fu
>            Assignee: Dian Fu
>             Fix For: 1.99.7
>
>         Attachments: SQOOP-2539.001.patch, SQOOP-2539.002.patch, 
> SQOOP-2539.003.patch, SQOOP-2539.004.patch, SQOOP-2539.005.patch
>
>
> Currently resource name such as job name, connector name or link name can be 
> null. We should enforce that these resource names cannot be null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to