[
https://issues.apache.org/jira/browse/SQOOP-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246166#comment-14246166
]
Veena Basavaraj commented on SQOOP-1900:
----------------------------------------
Well this exercise is about figuring that out since there are connectors that
benefit from non CSV if we are going to claim that SQOOP2 is generic and not
just for RDBMS like data sources.
I just dont see why this become handy in non text? , and also in case of non MR
engine, do we need this?
So I'd like to be educated about some concrete details on where these 2 methods
will add value.
> IDF API read/ write method
> ---------------------------
>
> Key: SQOOP-1900
> URL: https://issues.apache.org/jira/browse/SQOOP-1900
> Project: Sqoop
> Issue Type: Sub-task
> Components: sqoop2-framework
> Reporter: Veena Basavaraj
> Fix For: 1.99.5
>
>
> At this point I am not clear what the real use of the following 2 methods are
> in the IDF API. Can anyone explain? I have not seen it used anywhere in the
> code I might be missing something
> {code}
> /**
> * Serialize the fields of this object to <code>out</code>.
> *
> * @param out <code>DataOuput</code> to serialize this object into.
> * @throws IOException
> */
> public abstract void write(DataOutput out) throws IOException;
> /**
> * Deserialize the fields of this object from <code>in</code>.
> *
> * <p>For efficiency, implementations should attempt to re-use storage in
> the
> * existing object where possible.</p>
> *
> * @param in <code>DataInput</code> to deseriablize this object from.
> * @throws IOException
> */
> public abstract void read(DataInput in) throws IOException;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
