[
https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993709#comment-15993709
]
ASF GitHub Bot commented on KAFKA-4343:
---------------------------------------
GitHub user norwood opened a pull request:
https://github.com/apache/kafka/pull/2960
KAFKA-4343: Expose Connector type in REST API
https://cwiki.apache.org/confluence/display/KAFKA/KIP-151+Expose+Connector+type+in+REST+API
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/norwood/kafka KIP-151
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2960.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 #2960
----
commit 412d137876e2bef3139643a13beeffd18201419a
Author: dan norwood <norw...@confluent.io>
Date: 2017-05-02T20:41:50Z
KIP-151: Expose Connector type in REST API
https://cwiki.apache.org/confluence/display/KAFKA/KIP-151+Expose+Connector+type+in+REST+API
----
> 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)
