You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2016/05/17 13:52:13 UTC

[jira] [Updated] (KAFKA-3316) Add Connect REST API to list available connector classes

     [ https://issues.apache.org/jira/browse/KAFKA-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismael Juma updated KAFKA-3316:
-------------------------------
    Fix Version/s:     (was: 0.10.1.0)

> 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: KafkaConnect
>    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)