[
https://issues.apache.org/jira/browse/SQOOP-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241375#comment-14241375
]
Jarek Jarcec Cecho commented on SQOOP-1870:
-------------------------------------------
The current contract of the modules is as follows:
* {{sqoop-spi}} should contact classes that connector developer should directly
extent. As such it's very light module that don't have much external
dependencies and is also used as dependency for {{sqoop-core}}.
* {{connector-sdk}} contains reusable pieces that connector developer can use
(but shouldn't extent). As this is place for "random code" dependencies for
this module can grow a lot and that is why this module should not be used as a
dependency for any other module in Sqoop other then connectors.
I'm not entirely clear how those current contracts translate to the newly
proposed {{connector-utils}} and {{sqoop-spi}} [~vybs]?
> IDF API and impementation package depednency
> --------------------------------------------
>
> Key: SQOOP-1870
> URL: https://issues.apache.org/jira/browse/SQOOP-1870
> Project: Sqoop
> Issue Type: Bug
> Components: sqoop2-framework
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
>
> Currently the IDF API is in connector SDK package,
> The right place for IDF API is sqoop-spi package since custom implementations
> of the IDF can be done in future.
> Instead today sqoop SPI that holds connectors depends on SDK which in fact
> should be the other way round, the connector API is the root and should not
> depend on its implemenation package.
> connector SDK was intended to hold concrete implementations and some extent
> utility classes that the connectors use, there is obvioulsy some leaks and
> execution engine even depends on connecto-rsdk
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
