[
https://issues.apache.org/jira/browse/SQOOP-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242009#comment-14242009
]
Jarek Jarcec Cecho commented on SQOOP-1706:
-------------------------------------------
I would personally prefer to have a product documentation as part of the
product itself. This will enable us to have documentation and and changes in
the same patch, which has been working for us very well in Sqoop 1 land. Very
nice side effect that [~gwenshap] already mentioned is that user also gets the
"correct" docs for their version, that is very convenient as well.
Please don't take me wrong, I'm all for using wiki (or google docs, ...) to
collaborate on design proposals or ideas. I just believe that the product
documentation should be part of the product itself.
> Add API doc for the IDF interface and Schema -> ColumnTypes
> -----------------------------------------------------------
>
> Key: SQOOP-1706
> URL: https://issues.apache.org/jira/browse/SQOOP-1706
> Project: Sqoop
> Issue Type: Sub-task
> Components: sqoop2-framework
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
> Attachments: FromTo_Schema_IDF.001.png
>
>
> Since there can be multiple implementation of the IDF and connectors can
> chose to use a their specific implementation for IDF, document this as a
> PUBLIC apis
> Schema is part of the IDF interface and it is important to explain the
> different column types we support and how in one of the implementations we
> has certain assumptions for parsing from string to obejct
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
