You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Status

Current state: Under discussion

Discussion threadhere

JIRAKAFKA-5657

Released: 1.0.0.0

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

Currently we don't expose information about whether a connector is a source or sink in its description. 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.

Public Interfaces

We will modify the following REST API endpoint for Connect:

GET /connectors

Proposed Changes

The aforementioned endpoint currently returns the following structure:

HTTP/1.1 200 OK
Content-Type: application/json

["my-jdbc-source", "my-hdfs-sink"]
We will add a `type` field to each element of the array that indicates whether the given Connector is a Source or SInk. e.g.:

 

[ 
  { 
    "name": "my-jdbc-source",
    "type": "source",
  },
  { 
    "name": "my-hdfs-sink",
    "type": "sink",
  }
]

 

Compatibility, Deprecation, and Migration Plan

  • This is purely an addition to the current API and is backwards compatible.

Rejected Alternatives

The current method to get this information is to use a heuristic (does a class contain SInk/Source?), or use a lookup table. Neither of which works in every case, or with dynamically loaded Connectors.

  • No labels