sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sqoop QA bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1629) Sqoop2: Add unique constraint on the Config table for name and type
Date Tue, 28 Oct 2014 21:15:34 GMT

    [ 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

{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

View raw message