[
https://issues.apache.org/jira/browse/KAFKA-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200321#comment-15200321
]
ASF GitHub Bot commented on KAFKA-3316:
---------------------------------------
GitHub user Ishiihara opened a pull request:
https://github.com/apache/kafka/pull/1090
[KAFKA-3316]: Add REST API for listing connector plugins
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Ishiihara/kafka kafka-3316
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1090.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1090
----
commit 2071b6223532279be05928965112a99782675a20
Author: Liquan Pei <liquan...@gmail.com>
Date: 2016-03-16T22:09:32Z
add list connector plugins
----
> Add Connect REST API to list available connector classes
> --------------------------------------------------------
>
> Key: KAFKA-3316
> URL: https://issues.apache.org/jira/browse/KAFKA-3316
> Project: Kafka
> Issue Type: Bug
> Components: copycat
> Reporter: Ewen Cheslack-Postava
> Assignee: Liquan Pei
> Priority: Blocker
> Fix For: 0.10.0.0
>
>
> Each worker process's REST API should have an endpoint that can list
> available connector classes. This can use the same Reflections code as we
> used in KAFKA-2422 to find matching connector classes based on a short name.
> This is useful both for debugging and for any systems that want to work with
> different connect clusters and be able to tell which clusters support which
> connectors.
> We may need a new top-level resource to support this. We have /connectors
> already, but that refers to instantiated connectors that have been named. In
> contrast, this resource would refer to the connector classes
> (uninstantiated). We might be able to use the same resource to, e.g., lookup
> config info in KAFKA-3315 (which occurs before connector instantiation).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
