[
https://issues.apache.org/jira/browse/SQOOP-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187161#comment-14187161
]
Veena Basavaraj edited comment on SQOOP-1629 at 10/28/14 5:43 PM:
------------------------------------------------------------------
Sure, I think Abe you have a ver good point.
How about adding the connector/ configurbale Id to the constraint as well so we
make it explicit what we wanted. Atleast within a connector we want uniqueness,
so this will enforce it at database level.
Second, from the point of view of SQOOP-1515 we should just stick to using
config Ids for reusability. So when creating a LINK or JOB I can give the
link-config Id= 1 and then similalry for from/to/driver, since names will not
be unique across the entire set of configs.
was (Author: vybs):
Sure, I think Abe you have a ver good point.
How about adding the connector/ configurbale Id to the constraint as well so we
make it explicit what we wanted. Atleast within a connector we want uniqueness,
so this will enforce it at database level.
Second, from the point of view of SQOOP-1515 we should just stick to using
config Ids for reusability. So when creating a LINK or JOB I can give the
link-config Id= 1 and then similalry for from/to/driver
> 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: Sub-task
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
