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

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

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

Jarek Jarcec Cecho resolved SQOOP-455.
--------------------------------------

    Resolution: Invalid

I believe that this issue was resolved by introducing warning message in SQOOP-529. Basically --driver parameter was intended to be bound with Generic JDBC connector and therefore this is expected behavior.

Jarcec
                
> OracleManager not properly initialized when specifying --driver "oracle.jdbc.OracleDriver" in the command line 
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-455
>                 URL: https://issues.apache.org/jira/browse/SQOOP-455
>             Project: Sqoop
>          Issue Type: Bug
>          Components: connectors/oracle
>    Affects Versions: 1.4.1-incubating
>            Reporter: Weidong Bian
>            Priority: Minor
>
> 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);
>     }

--
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