[ 
https://issues.apache.org/jira/browse/SQOOP-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240426#comment-14240426
 ] 

Veena Basavaraj edited comment on SQOOP-1870 at 12/10/14 12:53 AM:
-------------------------------------------------------------------

thanks [~hshreedharan]
Might be a good idea to move the CSV Implementation to the SPI as well, if we 
are going to use this as  default.

Any utils can left in the connector-utils package, so we know that only 
utilities are in that package and nothing else.

[~jarcec] this seems much cleaner to avoid the cyclic dependency going forward 
and having a dilemma on where should connector core classes reside.


was (Author: vybs):
thanks [~hshreedharan]
Might be a good idea to move the CSV Implementation to the SPI as well, if we 
are going to use this as  default. 

> 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)

Reply via email to