[
https://issues.apache.org/jira/browse/SQOOP-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996753#comment-14996753
]
Jarek Jarcec Cecho commented on SQOOP-2674:
-------------------------------------------
I was recently looking into the code base and I have to agree that supporting
both numeric id and name is complicating the code base a lot. I'm concerned
about it because it means that pretty much for every REST call, we have two
code paths and we're not properly testing that everywhere.
We originally started with id and added names later and we wanted to keep both
for backward compatibility. However looking into the code I feel that
supporting both will cause more problems that it helps to solve, so I'm +1 on
dropping the support for ids from public interfaces.
I'm expecting that this will be a bit bigger exercise, so don't hesitate divide
the change into several subtasks [~colin_mjj]!
> Sqoop2: Remove the id from public interfaces for conection/job/link
> -------------------------------------------------------------------
>
> Key: SQOOP-2674
> URL: https://issues.apache.org/jira/browse/SQOOP-2674
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Colin Ma
> Assignee: Colin Ma
> Fix For: 1.99.7
>
>
> Currently, sqoop2 support both conection/job/link id and name in all calls.
> It’s quite complicating entire code base. We should remove the id from public
> interface to simplify the code and maintenance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
