You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Weidong Bian (Created) (JIRA)" <ji...@apache.org> on 2012/03/06 08:54:59 UTC
[jira] [Created] (SQOOP-455) OracleManager not properly initialized
when specifying --driver "oracle.jdbc.OracleDriver" in the command line
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. Shouldn't it be put even 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SQOOP-455) OracleManager not properly initialized
when specifying --driver "oracle.jdbc.OracleDriver" in the command line
Posted by "Weidong Bian (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weidong Bian updated SQOOP-455:
-------------------------------
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);
}
was:
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. Shouldn't it be put even 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);
}
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira