[
https://issues.apache.org/jira/browse/SQOOP-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187173#comment-14187173
]
Gwen Shapira commented on SQOOP-1629:
-------------------------------------
For the purpose of configs as top-level (and reusable) objects, I think we are
actually looking at config+inputs pair, right? (i.e. config is just the keys,
we want unique for the config with the values entered by the user). So the
input tables (SQ_LINK_INPUT and SQ_JOB_INPUT) should have uniqueness, but not
the config itself?
> 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)
