You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2015/01/22 18:40:34 UTC

[jira] [Resolved] (SQOOP-1634) Updating JOB and LINK does more than one rest HTTP call. ( can be avoided)

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

Veena Basavaraj resolved SQOOP-1634.
------------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 1.99.6)
                   2.0.0

Does not provide much benefit, http calls are inexpensive here ( 1 or 2 )

> 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: Bug
>            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)