[
https://issues.apache.org/jira/browse/SQOOP-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162929#comment-14162929
]
Veena Basavaraj edited comment on SQOOP-1547 at 10/8/14 1:53 AM:
-----------------------------------------------------------------
The Current connector api requires the developer to create a configuration
class for Link/From/ To. One of the requirements that we should be supporting
is NullConfigurationClasses in the connector SDK that can be used in use cases
where a particular config type is not relevant, For instance the HttpConnector
may not necessarily have a linkConfigurationClass, so they should be able to
give a NullConfigurationClass. Similarly a NullConfig class.
Second, we think that the current list of config types ( LINK/ JOB) are
sufficient for the Connector and we do not foresee a new type to be required
for the Sqoop1 connectors.
Third, as part of the SQOOP-1557, we will add a ConfigurableType that will add
extensibility to create new entities to support new Config types.
A new type of config may be added, but in that case it could be a new
Configurable with a different set of workflow. So it will not be a
SqoopConnector, but could be a SqoopFoo. So we think the current Initializer/
Destroyer/Extractor apis solve the uses cases we have for the Sqoop
was (Author: vybs):
The Current connector api requires the developer to create a configuration
class for Link/From/ To. One of the requirements that we should be supporting
is NullConfigurationClasses in the connector SDK that can be used in use cases
where a particular config type is not relevant, For instance the HttpConnector
may not necessarily have a linkConfigurationClass, so they should be able to
give a NullConfigurationClass. Similarly a NullConfig class.
Second, we think that the current list of config types ( LINK/ JOB) are
sufficient for the Connector and we do not foresee a new type to be required
for the Sqoop1 connectors.
A new type of config may be added, but in that case it could be a new
Configurable with a different set of workflow. So it will not be a
SqoopConnector, but could be a SqoopFoo. So we think the current Initializer/
Destroyer/Extractor apis solve the uses cases we have for the Sqoop
> Sqoop2: Connector API stabilization
> -----------------------------------
>
> Key: SQOOP-1547
> URL: https://issues.apache.org/jira/browse/SQOOP-1547
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
