[
https://issues.apache.org/jira/browse/SQOOP-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260542#comment-14260542
]
Vinoth Chandar commented on SQOOP-1821:
---------------------------------------
As I understand this, for things to function smoothly, the external connector
jars need to be placed under the same tomcat classloader as the sqoop webapp.
(Tomcat creates a class loader for each webapp).
I can only think of two ways to achieve this :
1) Something like addtowar.sh to add the external connector jar onto the
sqoop.war. Then bounce the sqoop server.
2) in SqoopServer.initialize(), pull out its class loader and load the external
connector jars. This will most likely place the jars where we want them.
Thoughts?
> External connector loading in Sqoop2
> ------------------------------------
>
> 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
> Assignee: 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)
