[
https://issues.apache.org/jira/browse/SQOOP-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115976#comment-13115976
]
David Robson commented on SQOOP-350:
------------------------------------
Actually - I found a parameter to do this I believe.
If you add the parameter
sqoop.connection.factories=com.quest.oraoop.OraOopManagerFactory then this
should force the OraOop manager factory to be used.
It is a bit confusing because OraOop ignores the connection-manager setting -
should ManagerFactory plugins respect this setting? Or if a user sets this
should the DefaultManagerFactory be forced to be used?
> Add support for requiring that a connector be used, otherwise the job should
> fail
> ---------------------------------------------------------------------------------
>
> Key: SQOOP-350
> URL: https://issues.apache.org/jira/browse/SQOOP-350
> Project: Sqoop
> Issue Type: Improvement
> Components: connectors
> Affects Versions: 1.3.0
> Reporter: Ken Krugler
>
> There are situations where it is critical that a specific connector be used
> during a Sqoop. For example, if you have a table that doesn't have a suitable
> column for partitioning, and thus you're relying on OraOop's row-based
> partitioning, then it's critical that OraOop be used. If the Sqoop request
> falls back to the generic Oracle connector, this puts huge, unacceptable load
> on the database.
> The proposal is to add a -connector <class name> parameter, which will cause
> the job to fail unless it's handled by the connector (from
> sqoop.ConnFactory.getManager) with the matching class name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
