sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2629) Sqoop2: Add ability to "blacklist" connectors
Date Wed, 28 Oct 2015 03:16:27 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977639#comment-14977639

ASF subversion and git services commented on SQOOP-2629:

Commit f33554a19e287ec38e331d46bc8fad4ae1e5d9aa in sqoop's branch refs/heads/sqoop2 from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=f33554a ]

SQOOP-2629: Sqoop2: Add ability to "blacklist" connectors

(Abraham Fine via Jarek Jarcec Cecho)

> Sqoop2: Add ability to "blacklist" connectors
> ---------------------------------------------
>                 Key: SQOOP-2629
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2629
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.6
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Abraham Fine
>             Fix For: 1.99.7
>         Attachments: SQOOP-2629.patch
> We currently have bunch of connectors "in flight" that might not be ready to be used
but yet we're committing changes to one code base. As those connectors might not be ready
to be shipped, it would mean that we can't do Sqoop 2 release at all.
> As that is undesirable I would like to propose enhancing Sqoop 2 to allow administrator
to configure blacklist of connectors that simply won't be loaded on start up. We can use this
list for each release to mark all "in-flight" connectors. Benefit of this is, that we can
still ship the code, users can still use it and provide feedback, but only if they explicitly
enable it (and hence know what they are doing).
> Another benefit of having ability to blacklist certain connectors is that administrator
can use that to suppress build-in connectors that are not desirable in that particular environment.

This message was sent by Atlassian JIRA

View raw message