Veena Basavaraj created SQOOP-1901:
--------------------------------------
Summary: Supporting DRY code in new IDF impementations
Key: SQOOP-1901
URL: https://issues.apache.org/jira/browse/SQOOP-1901
Project: Sqoop
Issue Type: Sub-task
Reporter: Veena Basavaraj
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
extensing from CSVIDF and this cannot technically work since we have the
generic T that will be different for AvroIDF or JSON IDF
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
