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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 1.3.0
• Fix Version/s: 1.4.3
• Component/s: connectors
• Assignee: Unassigned
• Reporter: Kenneth William Krugler
• Created: 22/Sep/11 20:11
• Updated: 02/May/13 02:30
• Resolved: 12/Oct/12 20:50

Description

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.

Issue Links

• relates to: SQOOP-529 Enforce usage of --driver and --connection-manager parameters