You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Abraham Elmahrek (JIRA)" <ji...@apache.org> on 2014/10/28 07:31:41 UTC
[jira] [Updated] (SQOOP-1629) Sqoop2: Add unique constraint on the
Config table for name and type
[ https://issues.apache.org/jira/browse/SQOOP-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abraham Elmahrek updated SQOOP-1629:
------------------------------------
Summary: Sqoop2: Add unique constraint on the Config table for name and type (was: Add unique constraint on the Config table for name and type)
> 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: 1.99.4
>
> 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)