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

Hudson commented on SQOOP-2250:
-------------------------------

SUCCESS: Integrated in Sqoop2-hadoop200 #813 (See 
[https://builds.apache.org/job/Sqoop2-hadoop200/813/])
SQOOP-2250: Sqoop2: SQ_LINK_INPUT is missing a foreign key constraint (abe: 
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=a3362a2563c03f10f221002753b6d08b0d21f378)
* 
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
* 
repository/repository-common/src/main/java/org/apache/sqoop/repository/common/CommonRepositoryHandler.java
* 
repository/repository-derby/src/main/java/org/apache/sqoop/repository/derby/DerbyRepoConstants.java
* 
repository/repository-common/src/main/java/org/apache/sqoop/repository/common/CommonRepositoryInsertUpdateDeleteSelectQuery.java


> Sqoop2: SQ_LINK_INPUT is missing a foreign key constraint
> ---------------------------------------------------------
>
>                 Key: SQOOP-2250
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2250
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: sqoop2-derby-repository
>    Affects Versions: 1.99.4
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>             Fix For: 1.99.6
>
>         Attachments: SQOOP-2250-1.patch, SQOOP-2250-2.patch, 
> SQOOP-2250.patch, Screen Shot 2015-03-20 at 11.11.56 AM.png, Screen Shot 
> 2015-03-20 at 11.12.09 AM.png
>
>
> While working on 2113 tests, I figured there is a missing constraint on the 
> SQ_LINK_INPUT table.
> the FK to the INPUT table is missing post the upgrade changes in 1.99.4 
> release.



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

Reply via email to