kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dan norwood (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (KAFKA-4343) Connect REST API should expose whether each connector is a source or sink
Date Tue, 02 May 2017 20:17:04 GMT

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

dan norwood reassigned KAFKA-4343:
----------------------------------

    Assignee: dan norwood

> Connect REST API should expose whether each connector is a source or sink
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-4343
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4343
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>            Reporter: Ewen Cheslack-Postava
>            Assignee: dan norwood
>              Labels: needs-kip, newbie++
>
> Currently we don't expose information about whether a connector is a source or sink.
This is useful when, e.g., categorizing connectors in a UI. Given naming conventions we try
to encourage you *might* be able to determine this via the connector's class name, but that
isn't reliable.
> This may be related to https://issues.apache.org/jira/browse/KAFKA-4279 as we might just
want to expose this information on a per-connector-plugin basis and expect any users to tie
the results from multiple API requests together. An alternative that would probably be simpler
for users would be to include it in the /connectors/<name>/status output.
> Note that this will require a KIP as it adds to the public REST API.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message