[
https://issues.apache.org/jira/browse/SQOOP-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252009#comment-17252009
]
Piyush Patel commented on SQOOP-2927:
-------------------------------------
Definitely an issue with Sqoop version 1.4.6. I was using Sqoop 1.4.6-cdh5.15.1
version.
The problem I faced was that when we had couple of drivers for mysql (5.1.38
and 8.0.22), we had to expliticly specify the version. I tried using `-libjar`
option which seemed to work only on few occassions, but it was random. It fails
sometimes.
However, using HADOOP_CLASSPATH it runs perfectly.
If this is the case, then either documentation needs to be updated or there
must be option or fix to specify explicit driver path.
> Add the ability to specify the location of a jdbc driver via command option
> ---------------------------------------------------------------------------
>
> Key: SQOOP-2927
> URL: https://issues.apache.org/jira/browse/SQOOP-2927
> Project: Sqoop
> Issue Type: Improvement
> Affects Versions: 1.4.6
> Reporter: thomas scott
> Priority: Minor
>
> User should be able to specify the location of a jdbc driver as an option
> during sqoop invocation. e.g.
> sqoop import --driver-location /tmp/ojdbc6.jar ...
> Also, the help suggests this is possible using -libjars and executing using
> bin/hadoop but this does not seem to work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
