Jarek Jarcec Cecho created SQOOP-529:
----------------------------------------
Summary: Enforce usage of --driver and --connection-manager
parameters
Key: SQOOP-529
URL: https://issues.apache.org/jira/browse/SQOOP-529
Project: Sqoop
Issue Type: Improvement
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 1.4.2
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.
--
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
