[
https://issues.apache.org/jira/browse/SQOOP-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132587#comment-14132587
]
Abraham Elmahrek edited comment on SQOOP-1509 at 9/13/14 7:15 AM:
------------------------------------------------------------------
It seems like the above document defines some kind of hierarchy with
'/config/<cfType>/link/<link name>'. Configs are provided by connectors right?
So then, connector developers and consumers of this API would logically look
for '/connector/<name>/config/<type>' or something of that nature. I think
'v1/connector/<cname>/link' is intended to cover this, but it's less intuitive
I think.
The most important thing is that all capabilities we currently have transfers
over to these new APIs.
was (Author: abec):
It seems like the above document defines some kind of hierarchy with
'/config/{cfType}/link/{link name}'. Configs are provided by connectors right?
So then, connector developers and consumers of this API would logically look
for '/connector/{name}/config/{type}' or something of that nature. I think
'v1/connector/{cname}/link' is intended to cover this, but it's less intuitive
I think.
The most important thing is that all capabilities we currently have transfers
over to these new APIs.
> Sqoop2: Sqoop2 Rest API refactoring
> -----------------------------------
>
> Key: SQOOP-1509
> URL: https://issues.apache.org/jira/browse/SQOOP-1509
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Attachments: SimplifySQOOPRESTAPIs.pdf
>
>
> See the attached DOC that explains the Rest APIs for the Sqoop entities
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
