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 2014/05/18 23:23:43 UTC
[jira] [Created] (SQOOP-1321) Add ability to serialize SqoopOption
into JobConf
Jarek Jarcec Cecho created SQOOP-1321:
-----------------------------------------
Summary: 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
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)