[
https://issues.apache.org/jira/browse/SQOOP-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114386#comment-13114386
]
David Robson commented on SQOOP-350:
------------------------------------
Actually the connection-manager does not do exactly what Ken wants here.
The connection-manager parameter is for the DefaultManagerFactory to tell it
what GenericJdbcManager to use. The Quest Data Connector for Oracle and Hadoop
works by implementing its own manager factory - OraOopManagerFactory. So in the
case a user specifies connection-manager - the OraOopManagerFactory could still
process the job anyway as it does not look at this parameter.
Would it be possible to have a connection-manager-factory property? This was
you could force Sqoop to use the OraOopManagerFactory, or if you wanted to use
the connection-manager parameter, you could specify
--connection-manager-factory=DefaultManagerFactory --connection-manager=...
Ken is currently experiencing a side effect of this parameter in that if you
specify an invalid class here, OraOopManagerFactory will still process the job,
but if it doesn't, when the DefaultManagerFactory is used after that it will
fail.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
