[
https://issues.apache.org/jira/browse/SQOOP-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246361#comment-14246361
]
Jarek Jarcec Cecho commented on SQOOP-1900:
-------------------------------------------
I would assume that we change the code for all IDF implementations including
CSV IDF. I'm wondering why we have not done that already, so I'm assuming that
there is some tricky edge case that needs to be handled.
> 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)
