[SQOOP-1803] Sqoop2: Update and save configuration upon job success

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.99.7
• Component/s: sqoop2-framework, sqoop2-jdbc-connector
• Assignee: Jarek Jarcec Cecho
• Reporter: Veena Basavaraj
• Created: 24/Nov/14 23:34
• Updated: 21/Apr/15 00:48
• Resolved: 21/Apr/15 00:36

Description

The details are in the design wiki, as the implementation happens more discussions can happen here.

https://cwiki.apache.org/confluence/display/SQOOP/Delta+Fetch+And+Merge+Design#DeltaFetchAndMergeDesign-Howtogetoutputfromconnectortosqoop?

The goal is to dynamically inject a IncrementalConfig instance into the FromJobConfiguration. The current MFromConfig and MToConfig can already hold a list of configs, and a strong sentiment was expressed to keep it as a list, why not for the first time actually make use of it and group the incremental related configs in one config object

This task will prepare the FromJobConfiguration from the job config data, ExtractorContext with the relevant values from the prev job run

This task will prepare the ToJobConfiguration from the job config data, LoaderContext with the relevant values from the prev job run if any

We will use DistributedCache to get State information from the Extractor and Loader out and finally persist it into the sqoop repository depending on SQOOP-1804 once the outputcommitter commit is called

Issue Links

• requires: SQOOP-2305 Sqoop2: ConfigUtils is not properly serializing Enum values
• links to: RB
• links to: Review board