[
https://issues.apache.org/jira/browse/SQOOP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13528308#comment-13528308
]
Kathleen Ting commented on SQOOP-626:
-------------------------------------
To be clear, the Sqoop User Guide already mentions that while working with
Oracle, you may encounter a problem when the Sqoop command explicitly specifies
the --driver <driver name> option. That is, when the driver option is included
in the Sqoop command, the built-in connection manager selection defaults to the
generic connection manager, which causes this issue with Oracle. If the driver
option is not specified, the built-in connection manager selection mechanism
selects the Oracle specific connection manager which generates valid SQL for
Oracle and uses the driver "oracle.jdbc.OracleDriver". This needs to be
extended for all connection managers, not just Oracle. Thanks for taking this
on Linden. Please advise on any questions - happy to assist.
> Sqoop User Guide's troubleshooting section should specify that "--driver"
> parameter should not be used for connection managers
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SQOOP-626
> URL: https://issues.apache.org/jira/browse/SQOOP-626
> Project: Sqoop
> Issue Type: Improvement
> Components: docs
> Affects Versions: 1.4.2
> Reporter: Kathleen Ting
> Assignee: Linden Hillenbrand
> Priority: Minor
> Labels: newbie
>
> Sqoop User Guide's troubleshooting section should specify that "--driver"
> parameter should not be used for connection managers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
