Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id ACFE02009DC for ; Tue, 2 May 2017 22:17:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AB8BA160BAB; Tue, 2 May 2017 20:17:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EDD1A160B9D for ; Tue, 2 May 2017 22:17:06 +0200 (CEST) Received: (qmail 43150 invoked by uid 500); 2 May 2017 20:17:06 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 43129 invoked by uid 99); 2 May 2017 20:17:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 May 2017 20:17:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 976B71A00AD for ; Tue, 2 May 2017 20:17:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 0K9HfX75Hss4 for ; Tue, 2 May 2017 20:17:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id B9A695F4A7 for ; Tue, 2 May 2017 20:17:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 57678E0905 for ; Tue, 2 May 2017 20:17:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 0D90121D90 for ; Tue, 2 May 2017 20:17:04 +0000 (UTC) Date: Tue, 2 May 2017 20:17:04 +0000 (UTC) From: "dan norwood (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (KAFKA-4343) Connect REST API should expose whether each connector is a source or sink MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 02 May 2017 20:17:07 -0000 [ 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//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)