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 "Aaron Kimball (JIRA)" <ji...@apache.org> on 2009/09/24 20:21:16 UTC
[jira] Updated: (MAPREDUCE-1036) An API Specification for Sqoop
[ https://issues.apache.org/jira/browse/MAPREDUCE-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Kimball updated MAPREDUCE-1036:
-------------------------------------
Attachment: sqoop-reference.txt
Attaching a draft of the API reference. After the open questions are discussed, I will upload a final version of this document formatted as a patch which extends the existing user-facing documentation.
> 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: 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.