[ 
https://issues.apache.org/jira/browse/SQOOP-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244803#comment-14244803
 ] 

Veena Basavaraj edited comment on SQOOP-1706 at 12/12/14 9:30 PM:
------------------------------------------------------------------

There needs to be balance between been productive. .rst format takes more than 
a simple wiki and second, simple changes need a wait and review that adds to a 
process that is uncalled for.

The wiki clearly says the doc is relevant for 1.99.5 release so that should 
solve to a good extent the problem with versioning.
I would suggest creating a pre release process to dump wikis into .rst so it is 
reviewed and ready to go. I am all for it, Anyone could do it.




was (Author: vybs):
There needs to be balance between been productive. .rst format takes more than 
a simple wiki and second, simple changes need a wait and review that adds to a 
process that is uncalled for.

I would suggest creating a pre release process to dump wikis into .rst so it is 
reviewed and ready to go. 

> Add IDF API doc/wiki  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)

Reply via email to