Jarek Jarcec Cecho created SQOOP-2629:
-----------------------------------------
Summary: 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
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)
