[
https://issues.apache.org/jira/browse/SQOOP-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081490#comment-15081490
]
Jarek Jarcec Cecho commented on SQOOP-2673:
-------------------------------------------
I'll do all those changes in separate JIRAs (separate patches).
> Sqoop2: Remove the notion of LinksBeans and JobsBeans
> -----------------------------------------------------
>
> Key: SQOOP-2673
> URL: https://issues.apache.org/jira/browse/SQOOP-2673
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
>
> Originally we had one bean object for jobs and one for links that was able to
> transfer one or more links/jobs. It seems that current code base has
> separated that into {{LinkBean}} for one object and {{LinksBean}} for
> multiple objects (same for job). Searching git and JIRA history I did not
> find proper discussion nor reasoning for this change. I see several
> challenges with this concept:
> * It's making one REST interface return different types depending on input
> values
> * It's making both client and server code difficult because we have to
> separate the cases everywhere
> It seems that this new concept has been extended to all returnable objects
> (Connectors, links, jobs, privileges, ...), so the change will be quite
> intrusive. Any objections if I return it back?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
