[
https://issues.apache.org/jira/browse/KAFKA-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liquan Pei updated KAFKA-3316:
------------------------------
Affects Version/s: 0.10.0.0
Status: Patch Available (was: In Progress)
> 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
> Affects Versions: 0.10.0.0
> 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)
