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

Hudson commented on SQOOP-1629:
-------------------------------

FAILURE: Integrated in Sqoop2-hadoop100 #633 (See 
[https://builds.apache.org/job/Sqoop2-hadoop100/633/])
SQOOP-1629: Sqoop2: Add unique constraint on the Config table for name and type 
(abraham: 
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=31f30cc279471ebe3a2d02f913e98d82a0e4a239)
* 
repository/repository-derby/src/test/java/org/apache/sqoop/repository/derby/TestRespositorySchemaUpgrade.java
* 
repository/repository-derby/src/test/java/org/apache/sqoop/repository/derby/TestInputTypes.java
* 
repository/repository-derby/src/test/java/org/apache/sqoop/repository/derby/TestConnectorHandling.java
* 
repository/repository-derby/src/main/java/org/apache/sqoop/repository/derby/DerbySchemaConstants.java
* 
repository/repository-derby/src/main/java/org/apache/sqoop/repository/derby/DerbyRepositoryHandler.java
* 
repository/repository-derby/src/main/java/org/apache/sqoop/repository/derby/DerbySchemaUpgradeQuery.java
* 
repository/repository-derby/src/test/java/org/apache/sqoop/repository/derby/DerbyTestCase.java


> Sqoop2: Add unique constraint on the Config table for name and type
> -------------------------------------------------------------------
>
>                 Key: SQOOP-1629
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1629
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>             Fix For: 2.0.0
>
>         Attachments: SQOOP-1629.patch, SQOOP-1629.patch, SQOOP-1629.patch, 
> SQOOP-1629.patch, SQOOP-1629.patch, SQOOP-1629.patch
>
>
> this helps create top level config objects and use their names while creating 
> the LINK and JOB entities
> After some discussion, we do not unique configs across the whole sqoop, 
> unique per configurable and config type is what we want. It is how we have it 
> but just the database constraint was not enforced, this ticket adds it



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

Reply via email to