[
https://issues.apache.org/jira/browse/SQOOP-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608498#comment-14608498
]
Rakesh Sharma commented on SQOOP-2333:
--------------------------------------
Venkat suggested us to compare extraarguments as well for the requirement. I
explored extra arguments if we could use them rather than using custom tool
options. I feel that it will not be appropriate to use extra arguments for user
defined tools. Following are some pros for custom tool options for user defined
tools:
- extra-arguments are designed for subprograms which are used by sqoop and are
not for sqoop tools
- Extra-arguments are not parsed and are available as a string array which can
be passed to the subprograms. Subprograms can directly use these as s and it is
the subprogram which understands them. In our case , we need them to be parsed
and readily available through out processing. SqoopOptions is the state object
which is passed through out program even to M/R and we want that our options
should be readily available. If we pass them as array and don’t parse it, we
need to parse it every where we are using it. It will not be appropriate to do
it. So if we parse them and pass it as a map, it will be readily available.
- extraArguments are not stored on meta store and it won’t be possible to
create a run jobs of new tool.
- Extra-arguments are not validated as well. They are supposed to be passed to
the subprogram (like mysqldump) directly.
I believe, customTool Options will be a great addition for developers. It is
in-line with sqoop design and tool based architecture. It opens up option for
developer to add new options for their developed plugins.It also supports
storing them in metastore so that user can also persist their jobs in sqoop
metastore.
> Sqoop to support Custom options for User Defined Plugins(Tool)
> --------------------------------------------------------------
>
> Key: SQOOP-2333
> URL: https://issues.apache.org/jira/browse/SQOOP-2333
> Project: Sqoop
> Issue Type: New Feature
> Affects Versions: 1.4.5
> Reporter: Atul Gupta
> Assignee: Rakesh Sharma
> Fix For: 1.4.7
>
> Attachments: SQOOP-2333_0.patch
>
>
> Sqoop currently does not provide any mechanism to define custom switches for
> the user defined tools. it would be nice if we can enhance Sqoop to support
> user defined Custom Tool options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)