[
https://issues.apache.org/jira/browse/SQOOP-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971752#comment-14971752
]
Jarek Jarcec Cecho commented on SQOOP-2634:
-------------------------------------------
I think that we're mixing multiple things together in this JIRA, so let me try
unwrapping them.
The property {{org.apache.sqoop.classpath.extra}} is not meant to be used by
the connectors themselves. It's for Sqoop administrators to configure
additional jars that should be loaded to Sqoop 2 server (additional
repositories, submission or execution engines, ...). As a result, we should not
eliminate the property - it's very helpful :)
Installing a new connector should be as simple as possible and even go as far
as that installing connector is just about copying the connector's jar to Sqoop
classpath (for example by including it in the property above). I think that
forcing the users to copy the jar around *and* configure the classpath would be
undesirable - it's very easy to do that wrong (typos in classpath, ...). I
think that we should came up with a system where the connector itself will
expose the required classpath. We already have basics of that in
[{{Initializer.getJars}}|https://github.com/apache/sqoop/blob/sqoop2/connector/connector-sdk/src/main/java/org/apache/sqoop/job/etl/Initializer.java#L63]
where the connector is providing us the jars that are required for the
execution engine. I think that we should refactore this to a general way how
the connectors will expose classpath.
It seems as large topic, so one pager outlining various options is definitely
in place.
> Sqoop2: Allow connectors to express jar dependencies
> ----------------------------------------------------
>
> Key: SQOOP-2634
> URL: https://issues.apache.org/jira/browse/SQOOP-2634
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Dian Fu
> Assignee: Dian Fu
> Fix For: 1.99.7
>
> Attachments: SQOOP-2634.001.patch, SQOOP-2634.002.patch,
> SQOOP-2634.003.patch, SQOOP-2634.004.patch, SQOOP-2634.005.patch
>
>
> Currently Sqoop 2 has already provided the ability to config jar dependencies
> with property "org.apache.sqoop.classpath.extra". The limitation of this
> property is that we have to put all the dependencies together. It can't
> express jar dependencies for a specified connector. This capacity is useful
> as some connectors may have conflict jar dependencies. Put all the
> dependencies from different connectors together may cause problems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
