[
https://issues.apache.org/jira/browse/SQOOP-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234416#comment-14234416
]
Vinoth Chandar commented on SQOOP-1821:
---------------------------------------
The problem with tomcat is the mess or sophistication (depending on how much
tomcat you know), around class loaders
(http://www.mulesoft.com/tcat/tomcat-classpath)
Jarek is right : All the sqoop server needs to do to load external jars should
a call to the JVM class loader on startup..
Can we switch to something like Netty instead? (I see a ticket for Jetty
already). If REST endpoints is all that Tomcat is buying us, then probably not
worth it. Could simplify this a lot.
> DOC: Add instructions on how-to create a external connector and make it work
> in Sqoop
> -------------------------------------------------------------------------------------
>
> Key: SQOOP-1821
> URL: https://issues.apache.org/jira/browse/SQOOP-1821
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.5
> Reporter: Veena Basavaraj
> Fix For: 1.99.5
>
>
> Edit this wiki to begin with
> https://cwiki.apache.org/confluence/display/SQOOP/Setting+up+Sqoop+2#SettingupSqoop2-InstallinganewconnectortoSqoop2
> Also, add the same to the .rst of need be
> relevant code that loads all connectors
> https://github.com/apache/sqoop/blob/sqoop2/core/src/main/java/org/apache/sqoop/connector/ConnectorManagerUtils.java#L44
> NOTE : External contributors had issues with getting a new sqoop connector
> working seamlessly with the Sqoop2. They had to do some hacks to include this
> new jar into the class path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
