Return-Path: X-Original-To: apmail-sqoop-dev-archive@www.apache.org Delivered-To: apmail-sqoop-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8D7A117965 for ; Tue, 28 Oct 2014 21:15:34 +0000 (UTC) Received: (qmail 5220 invoked by uid 500); 28 Oct 2014 21:15:34 -0000 Delivered-To: apmail-sqoop-dev-archive@sqoop.apache.org Received: (qmail 5174 invoked by uid 500); 28 Oct 2014 21:15:34 -0000 Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sqoop.apache.org Delivered-To: mailing list dev@sqoop.apache.org Received: (qmail 5161 invoked by uid 99); 28 Oct 2014 21:15:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2014 21:15:34 +0000 Date: Tue, 28 Oct 2014 21:15:34 +0000 (UTC) From: "Sqoop QA bot (JIRA)" To: dev@sqoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SQOOP-1629) Sqoop2: Add unique constraint on the Config table for name and type MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SQOOP-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187482#comment-14187482 ] Sqoop QA bot commented on SQOOP-1629: ------------------------------------- Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12677691/SQOOP-1629.patch against branch sqoop2. {color:green}Overall:{color} +1 all checks pass {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 {color:green}SUCCESS:{color} All tests passed Console output: https://builds.apache.org/job/PreCommit-SQOOP-Build/475/console This message is automatically generated. > 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 > > > 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)