[
https://issues.apache.org/jira/browse/SQOOP-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158090#comment-13158090
]
Ken Krugler commented on SQOOP-365:
-----------------------------------
The three biggest challenges we ran into using Sqoop were:
1. Needing better control over the connection process. E.g. being able to set
the connection timeout.
2. Password management. Since passwords can be managed via a separate system,
making it easy to integrate with such a system would be critical for at least
one of our clients. The key is avoiding passwords on the command line, in
logging, and being sent in the clear to slaves in the cluster.
3. Synchronization with third party plugins (primarily OraOop). As new
functionality is added to core Sqoop, currently it seems like there's a
significant burden placed on the plug-in developer to keep in sync, or to
detect/handle the existence (or not) of some new functionality. Improving ease
of extension will hopefully also address issues with ease of compatibility.
-- Ken
> Proposal for next major revision of Sqoop.
> ------------------------------------------
>
> Key: SQOOP-365
> URL: https://issues.apache.org/jira/browse/SQOOP-365
> Project: Sqoop
> Issue Type: Wish
> Reporter: Arvind Prabhakar
> Assignee: Arvind Prabhakar
> Attachments: sqoop2.tar.gz
>
>
> This issue tracks the design and development of the next major revision of
> Sqoop. The proposal has been articulated on the wiki at the following
> location:
> https://cwiki.apache.org/confluence/display/SQOOP/Sqoop+2
> Please review the proposal and add your comments to this JIRA.
--
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
