[
https://issues.apache.org/jira/browse/SQOOP-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002022#comment-14002022
]
ASF subversion and git services commented on SQOOP-1321:
--------------------------------------------------------
Commit 18f5b2a77e95e412e806cabf4080a991f79aca92 in sqoop's branch
refs/heads/trunk from [~nrv]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=18f5b2a ]
SQOOP-1321: Add ability to serialize SqoopOption into JobConf
(Jarek Jarcec Cecho via Venkat Ranganathan)
> Add ability to serialize SqoopOption into JobConf
> -------------------------------------------------
>
> Key: SQOOP-1321
> URL: https://issues.apache.org/jira/browse/SQOOP-1321
> Project: Sqoop
> Issue Type: Improvement
> Affects Versions: 1.4.4
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.4.5
>
> Attachments: SQOOP-1321.patch, SQOOP-1321.patch
>
>
> While working on various user issues, I've several times came into need to
> see what exact parameters were used when starting Sqoop. This seems
> relatively easy, but can get complicated when users are using some scripts on
> top of Sqoop binary or are directly integrating with the unsupported Java API.
> Hence I would like to propose to add option to simply dump entire
> {{SqoopOptions}} class into created {{Job}} object and make the used
> parameters available and persisted in the {{job.xml}}.
> This will also enable audit tools that are inspecting {{job.xml}} for various
> information.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
