[SQOOP-2047] Optimal Connector Upgrade API

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Fix Version/s: 2.0.0
• Assignee: Unassigned
• Reporter: Veena Basavaraj
• Created: 24/Jan/15 17:00
• Updated: 21/Oct/15 20:41
• Resolved: 21/Oct/15 20:41

Description

As described in the parent ticket, the connector upgrade code can become a bit more smarter.

It does not have to dump every single input/ config and its values on every connector upgrade path, irrespective of anything changed or not.

We can just ask the connector to provide a list of keys that changed.

for new ones, for old ones and the deleted ones

New one, assuming foo does not exist, a new record will be created

"foo" : { "name" : "foo" , type : "String" , value : "default"}

Modified one, assuming foo exists, we will look up and modify, per connector per job ( since it will modify for all jobs anyways, there is no way to have a different input name for job 1 and job2 )

{code
"foo" :

{ "name" : "bar" , type : "Integer" , value : "newValue"}

Delete a key

foo : "" ( empty) value