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] [Updated] (SQOOP-1634) Updating JOB and LINK does more than one rest HTTP call. ( can be avoided)
Date Wed, 29 Oct 2014 16:33:33 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Veena Basavaraj updated SQOOP-1634:
-----------------------------------
    Description: Instead of having to get the link config/ from config/ to config every time
we create a job, we can have a client API to create ( or rather populate is the right word)
the values for the connector and driver configs and use these ids while creating the job.
We do not need to make a call in the client to fetch the connector associated with the link
everytime.
        Summary: Updating JOB and LINK does more than one rest HTTP call. ( can be avoided)
 (was: Updating JOB and LINK more than one rest calls. ( can be avoided))

> Updating JOB and LINK does more than one rest HTTP call. ( can be avoided)
> --------------------------------------------------------------------------
>
>                 Key: SQOOP-1634
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1634
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Veena Basavaraj
>             Fix For: 2.0.0
>
>
> Instead of having to get the link config/ from config/ to config every time we create
a job, we can have a client API to create ( or rather populate is the right word) the values
for the connector and driver configs and use these ids while creating the job. We do not need
to make a call in the client to fetch the connector associated with the link everytime.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message