You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2012/07/31 22:50:34 UTC
[jira] [Created] (SQOOP-529) Enforce usage of --driver and
--connection-manager parameters
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
[jira] [Updated] (SQOOP-529) Enforce usage of --driver and
--connection-manager parameters
Posted by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Jarcec Cecho updated SQOOP-529:
-------------------------------------
Attachment: SQOOP-529.patch
> 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
>
> Attachments: SQOOP-529.patch, SQOOP-529.patch
>
>
> 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
[jira] [Updated] (SQOOP-529) Enforce usage of --driver and
--connection-manager parameters
Posted by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Jarcec Cecho updated SQOOP-529:
-------------------------------------
Attachment: SQOOP-529.patch
> 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
>
> Attachments: SQOOP-529.patch, SQOOP-529.patch, SQOOP-529.patch
>
>
> 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
[jira] [Updated] (SQOOP-529) Enforce usage of --driver and
--connection-manager parameters
Posted by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Jarcec Cecho updated SQOOP-529:
-------------------------------------
Attachment: SQOOP-529.patch
> 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
>
> Attachments: SQOOP-529.patch
>
>
> 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
[jira] [Commented] (SQOOP-529) Enforce usage of --driver and
--connection-manager parameters
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427774#comment-13427774 ]
Hudson commented on SQOOP-529:
------------------------------
Integrated in Sqoop-ant-jdk-1.6 #131 (See [https://builds.apache.org/job/Sqoop-ant-jdk-1.6/131/])
SQOOP-529: Enforce usage of --driver and --connection-manager parameters (Revision 1368748)
Result = SUCCESS
blee :
Files :
* /sqoop/trunk/src/java/org/apache/sqoop/ConnFactory.java
* /sqoop/trunk/src/java/org/apache/sqoop/manager/DefaultManagerFactory.java
> 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
>
> Attachments: SQOOP-529.patch, SQOOP-529.patch, SQOOP-529.patch
>
>
> 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