[
https://issues.apache.org/jira/browse/SQOOP-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234441#comment-14234441
]
Veena Basavaraj commented on SQOOP-1821:
----------------------------------------
[~vinothchandar] Switching to Netty is a a good option, but not imminent I
believe. Patches welcome.!
Tomcat's class loading is tricky, but it is not terrible that there are no
workarounds.
I started fixing the current code, but got busy with something else. So this is
in the top priority to fix.
There are options based on how the tomcat class loader
works:http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
http://stackoverflow.com/questions/13374217/load-libs-from-a-different-classloader-in-a-web-application
> 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)
