Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sqoop.apache.org
Date: Fri, 20 Mar 2015 18:09:42 +0000 (UTC)
From: "Veena Basavaraj (JIRA)" <jira@apache.org>
To: dev@sqoop.apache.org
Message-ID: <JIRA.12783704.1426874863000.159654.1426874982115@Atlassian.JIRA>
In-Reply-To: <JIRA.12783704.1426874863000@Atlassian.JIRA>
References: <JIRA.12783704.1426874863000@Atlassian.JIRA>
 <JIRA.12783704.1426874863689@arcas>
Subject: [jira] [Commented] (SQOOP-2250) SQ_LINK_INPUT in derby is missing a
 foreign key constraint
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Veena Basavaraj commented on SQOOP-2250:
----------------------------------------

if someone can also confirm this is an issue, I can send a patch. With my local testing, I do not see the FK from SQ_LINK_INPUT to the SQ_INPUT table with the latest code. This also causes issue with the update config / input code in SQOOP-2113 for link inputs.

[~jarcec] [~abec]

> SQ_LINK_INPUT in derby is missing a foreign key constraint
> ----------------------------------------------------------
>
>                 Key: SQOOP-2250
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2250
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Veena Basavaraj
>             Fix For: 1.99.6
>
>
> 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)