[jira] [Resolved] (SQOOP-350) Add support for requiring that a connector be used, otherwise the job should fail

["Jarek Jarcec Cecho (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SQOOP-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Jarcec Cecho resolved SQOOP-350.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4.3

I believe that this issue was resolved by SQOOP-529, where we moved handling of the --connecton-manager parameter out of default factory and thus enforce it's usage all the time. Please do not hesitate to reopen this issue if needed.
                
> 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
>             Fix For: 1.4.3
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira