[
https://issues.apache.org/jira/browse/SQOOP-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326777#comment-14326777
]
Veena Basavaraj commented on SQOOP-1511:
----------------------------------------
Could be revisited later, for now use the entire config objects
> Support the config resource Id parameter for creating JOB and LINK
> ------------------------------------------------------------------
>
> Key: SQOOP-1511
> URL: https://issues.apache.org/jira/browse/SQOOP-1511
> Project: Sqoop
> Issue Type: Bug
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 2.0.0
>
>
> My biggest qualms was when using the JSON api to post LINK and JOB.
> The post data has to meticulously include every single fields of the job
> config and all it inputs, I cant even by pass the optional ones, since there
> is some weird checking we do in the code. Yes it is pretty weird that we
> check that every non required field is in the POST data
> {code}
> MLink postedLink = links.get(0);
> MLinkConfig linkConfig = ConnectorManager.getInstance()
>
> .getConnectorConfigurable(postedLink.getConnectorId()).getLinkConfig();
> if (!linkConfig.equals(postedLink.getConnectorLinkConfig())) {
> throw new SqoopException(ServerError.SERVER_0003, "Detected incorrect
> link config structure");
> }
>
> {code}
> So I should be able to just add values to the config objects once and give
> that ID in the LINK and JOB creation
> NOTE: we do not allow creating configs and inputs from APIs/ command line. It
> is done via the code classes in the connectors and driver and it will remain
> so
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
