[
https://issues.apache.org/jira/browse/SQOOP-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136677#comment-14136677
]
Veena Basavaraj commented on SQOOP-1509:
----------------------------------------
[~abec] Yes, all capabilities transfer to the new APIs.
Here is one important change these apis will bring about in how we represent
object relationships underneath as well.
The ownership of the max-connections (more precisely the max tcp connections
allowed per physical database ) is currently in the driver/framework part of
the connection. In my proposal, The driver is directly unaware of the
connector/connection. There is no more ""framework part of the connection".
Driver only and must only know about Sqoop Jobs directly and everything else is
indirect. Driver will infer all the information it needs via the from/to and
driver configs.
Keeping driver decoupled from the connection is very important and the Configs
will act as the "MEDIATORS.
Driver can still own these configs related to connections, like it holds
extractors/ loaders. It is just a matter of been more descriptive of what
these configs are. Since the from/to refactoring we should probably have had 2
properties.
maxToConnectionFromTheDriver and maxFromConnectionsFromTheDriver
I also suggest we have a flat linear hierarchy of these configs, and we should
make sure that these config properties are very very descriptive, SecurityForm
and ThrottlingForm could mean different things in different context.
Second, I had missed the version resource. I will be adding it back. It will
not be removed.
Third, After discussions with the team, the pending question is how we
represent the resource urls.
i.e If we want v1/ connector/ {cname}/ link or v1/link ?cname=
I will double check with a couple of other uses cases in hdfs/yarn to come to a
conclusion on the above.
> 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)
