Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.4.4
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- links to