sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1629) Sqoop2: Add unique constraint on the Config table for name and type
Date Wed, 29 Oct 2014 01:07:35 GMT

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

ASF subversion and git services commented on SQOOP-1629:
--------------------------------------------------------

Commit 31f30cc279471ebe3a2d02f913e98d82a0e4a239 in sqoop's branch refs/heads/sqoop2 from [~abec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=31f30cc ]

SQOOP-1629: Sqoop2: Add unique constraint on the Config table for name and type

(Veena Basavaraj via Abraham Elmahrek)


> 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)

Mime
View raw message