[SQOOP-455] OracleManager not properly initialized when specifying --driver "oracle.jdbc.OracleDriver" in the command line

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: 1.4.1-incubating
• Component/s: connectors/oracle
• Assignee: Unassigned
• Reporter: Weidong Bian
• Created: 06/Mar/12 07:53
• Updated: 02/May/13 02:30
• Resolved: 12/Oct/12 21:43

Description

When specifying --driver "oracle.jdbc.OracleDriver" in cli,a GenericJdbcManager instead of OracleManager is initialized even when -connect-manager is specified due to the following code in org.apache.sqoop.manager.DefaultManagerFactory. Should have been put after the connection scheme is judged.

String manualDriver = options.getDriverClassName();
if (manualDriver != null)

{ // User has manually specified JDBC implementation with --driver. // Just use GenericJdbcManager. return new GenericJdbcManager(manualDriver, options); }

Issue Links

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