[
https://issues.apache.org/jira/browse/SQOOP-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183257#comment-14183257
]
Sqoop QA bot commented on SQOOP-1619:
-------------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12676963/SQOOP-1619.patch
against branch sqoop2.
{color:red}Overall:{color} -1 due to 2 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sqoop.repository.derby.TestRespositorySchemaUpgrade
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} Patch add/modify test case
{color:green}SUCCESS:{color} Patch compiled
Console output: https://builds.apache.org/job/PreCommit-SQOOP-Build/457/console
This message is automatically generated.
> Enforce Unique constraint for name on configurable table
> --------------------------------------------------------
>
> Key: SQOOP-1619
> URL: https://issues.apache.org/jira/browse/SQOOP-1619
> Project: Sqoop
> Issue Type: Bug
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.4
>
> Attachments: SQOOP-1619.patch
>
>
> We want to enforce unique connector and driver names.
> Also fix the tests for other unique name constraints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
