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 Tue, 06 Oct 2009 22:27:31 GMT

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

Aaron Kimball commented on MAPREDUCE-1036:

After ruminating on this for a while, here are the decisions I plan to implement:

* ImportOptions will contain a reference to the Configuration used when Sqoop's main() method
was invoked. This will be the preferred mechanism to send manager-specific data from the command
line (i.e., via {{-D k=v}} and ToolRunner/GenericOptionsParser).
* StreamHandlerFactory will be renamed to AsyncSink to be shorter. All child classes will
be renamed as well.
* Abstract classes will be used instead of interfaces for all externally-implemented APIs.
This affects ManagerFactory, ConnManager, and StreamHandlerFactory/AsyncSink. Going forward,
interfaces will only be used for objects internally created via factories whose implementations
are opaque to external clients, or to indicate the presence of a single method or behavior
(e.g., {{Closeable}}).

> 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