[
https://issues.apache.org/jira/browse/SQOOP-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977345#comment-14977345
]
Sqoop QA bot commented on SQOOP-2629:
-------------------------------------
Testing file
[SQOOP-2629.patch|https://issues.apache.org/jira/secure/attachment/12769080/SQOOP-2629.patch]
against branch sqoop2 took 0:57:33.386392.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} Patch add/modify test case
{color:green}SUCCESS:{color} License check passed
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All unit tests passed (executed 1544 tests)
{color:green}SUCCESS:{color} Test coverage did not decreased
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1822/artifact/patch-process/cobertura_report.txt])
{color:green}SUCCESS:{color} No new findbugs warnings
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1822/artifact/patch-process/findbugs_report.txt])
{color:green}SUCCESS:{color} All integration tests passed (executed 90 tests)
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1822/console].
This message is automatically generated.
> 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
> Attachments: SQOOP-2629.patch, 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
(v6.3.4#6332)
