[SQOOP-529] Enforce usage of --driver and --connection-manager parameters

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.2
• Assignee: Jarek Jarcec Cecho
• Reporter: Jarek Jarcec Cecho
• Created: 31/Jul/12 20:48
• Updated: 02/May/13 02:30
• Resolved: 02/Aug/12 23:06

Description

Choosing and creating connection manager instance is very tricky in current Sqoop code. Sqoop will defer the choice to loaded factory classes - only DefaultManagerFactory is used by default. This default class implements logic for --driver and --connection-manager parameters. However user also do have option to add own factories that do not necessarily have the same behavior.

This is very tricky as it actually depends on user environment (which factories are loaded) whether --driver and --connection-manager properties will work as expected (~ the same way all the time).

I would like to suggest putting logic around --driver and --connection-manager out of DefaultManagerFactory to enforce their usage in all cases.

Issue Links

• is related to: SQOOP-455 OracleManager not properly initialized when specifying --driver "oracle.jdbc.OracleDriver" in the command line
• is related to: SQOOP-350 Add support for requiring that a connector be used, otherwise the job should fail
• links to: Review board