You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2009/11/04 19:43:32 UTC

[jira] Commented: (MAPREDUCE-1036) An API Specification for Sqoop

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773604#action_12773604 ] 

Hudson commented on MAPREDUCE-1036:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #133 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/133/])
    

> An API Specification for Sqoop
> ------------------------------
>
>                 Key: MAPREDUCE-1036
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1036
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>          Components: contrib/sqoop
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>         Attachments: MAPREDUCE-1036.patch, sqoop-reference.txt
>
>
> Over the last several months, Sqoop has evolved to a state that is functional and has room for extensions. Developing extensions requires a stable API and documentation. I am attaching to this ticket a description of Sqoop's design and internal APIs, which include some open questions. I would like to solicit input on the design regarding these open questions and standardize the API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.