[SQOOP-1901] Sqoop2: Support DRY code in IDF impementations and add JSONIDF

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.99.5
• Component/s: sqoop2-framework
• Assignee: Veena Basavaraj
• Reporter: Veena Basavaraj
• Created: 14/Dec/14 18:57
• Updated: 06/Jan/15 03:59
• Resolved: 06/Jan/15 02:57

Description

As the title suggests, we want to encourage DRY code in the new IDF implementations.

As the IDF api mandates CSV and object format for all its sub implementation, I propose we move the common functionality to the base IDF class so that JSON IDF or AvroIDF does not have to repeat this code.

The only parts of the code that needs to be in subclasses is how then handle the conversion between the "T" ( generic parameter) and the csv/ object representations.

I saw that http://ingest.tips/2014/12/11/sqoop-1-99-4-release/ mentions extensind from CSVIDF and this cannot technically work since we have the generic T that will be different for AvroIDF or JSON IDF

Update:

Also extending from CSVIDF seems a bit ilogical, since the IDF API says that it needs CSV and object Array, these functionality of converting between the two i.e text to object and object to text should be in base class.

Issue Links

• links to: RB