You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Abraham Elmahrek (JIRA)" <ji...@apache.org> on 2013/04/12 19:26:15 UTC
[jira] [Commented] (SQOOP-773) Sqoop2: Batch execution support for
client commands
[ https://issues.apache.org/jira/browse/SQOOP-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630368#comment-13630368 ]
Abraham Elmahrek commented on SQOOP-773:
----------------------------------------
Batch execution for every client command can be supported by programmatically adding long command line options for all fields defined for a particular model (IE: MConnection, MJob, etc). The fields are defined in forms (IE: ConnectionForm, SecurityForm, etc). These classes can be found through the models defined in org.apache.sqoop.model in sqoop-common. A prefix can be added to discern between predefined options (IE: Max Connections) and a command option (IE: username).
> Sqoop2: Batch execution support for client commands
> ---------------------------------------------------
>
> Key: SQOOP-773
> URL: https://issues.apache.org/jira/browse/SQOOP-773
> Project: Sqoop
> Issue Type: Improvement
> Affects Versions: 1.99.1
> Reporter: Bilung Lee
> Assignee: Abraham Elmahrek
> Priority: Minor
>
> Currently, some clients commands (create, update, and clone) only support interactive mode even though the underlying Groovy shell infrastructure supports batch execution of commands. These commands need support for batch execution as well.
--
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