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

Compare with Current View Page History

Version 1 Next »

Status

Current state: Under Discussion

Discussion thread: TBD

JIRA: KAFKA-4343

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. 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 /connector-plugins

Proposed Changes

The aforementioned endpoint currently returns the following structure:

[ 
  { "class": "org.apache.kafka.connect.file.FileStreamSourceConnector" },
  { "class": "org.apache.kafka.connect.file.FileStreamSinkConnector" }
]
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.:

 

[ 
  { 
    "class": "org.apache.kafka.connect.file.FileStreamSourceConnector",
    "type": "SOURCE"
  },
  { "class": "org.apache.kafka.connect.file.FileStreamSinkConnector",
    "type": "SINK"
  }
]

 

Compatibility, Deprecation, and Migration Plan

  • What impact (if any) will there be on existing users?
  • If we are changing behavior how will we phase out the older behavior?
  • If we need special migration tools, describe them here.
  • When will we remove the existing behavior?

Rejected Alternatives

If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.

  • No labels