[
https://issues.apache.org/jira/browse/SQOOP-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-1629:
-----------------------------------
Description:
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
was:this helps create top level config objects and use their names while
creating the LINK and JOB entities
> 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
>
>
> 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)
