[
https://issues.apache.org/jira/browse/SQOOP-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-1511:
-----------------------------------
Description:
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}
was:instead of hav
> 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: Task
> 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}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
