sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Veena Basavaraj (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1629) Sqoop2: Add unique constraint on the Config table for name and type
Date Tue, 28 Oct 2014 18:19:34 GMT

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

Veena Basavaraj commented on SQOOP-1629:

Here is the use case. 

So I can say show me the "LINK" config for configurable = 1 and it will display all the fields
to populate and that will come out of the corresponding LINK or JOB INPUT. So this api in
SQOOP-1516 is only for update/ delete / display of its values. Since configs are created when
the configurables are registered.

Once the config values/ inputs are populated, I can just use the config Id in the input to
the LINK/ job creation. I dont have to fill it every time a job is created or link is created.
I can re use this.

Initially I thought I can use config names like we use in other places, does not seem like
a good idea since we want to support same names across connectors.

Hope this makes it clear.

As far as adding uniqueness to input names, it should be done, but very unrelated to this

We should make our DB much more complete by defining these constraints on all the tables we
have to going forward

> 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

View raw message