hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Kimball (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1036) An API Specification for Sqoop
Date Wed, 07 Oct 2009 18:25:34 GMT

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

Aaron Kimball commented on MAPREDUCE-1036:

In the same spirit as the "Context" objects provided to Mapper.map() and Reducer.reduce(),
I'm also going to modify ConnManager.importJob() to receive an ImportJobContext as its parameter.

> 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.

View raw message