Deploy a Kafka Connect source and sink connector

domain: kafka.apache.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Start a Kafka Connect worker with a worker.properties file specifying bootstrap.servers, plugin.path, and key/value converters
  2. Install connector JARs by placing them under the plugin.path directory and restarting the worker
  3. Register a source connector via POST to /connectors with JSON body containing name, config.connector.class, tasks.max, and connector-specific settings
  4. Register a sink connector similarly, specifying topics and the target system connection parameters
  5. Monitor connector status with GET /connectors/YOUR_CONNECTOR_NAME/status and tasks with GET /connectors/YOUR_CONNECTOR_NAME/tasks/0/status

Known gotchas

Related routes

Kafka Connect REST create connector
kafka.apache.org · 5 steps · unrated
Configure Kafka Connect with a custom SMT to mask or hash PII fields before records reach a sink connector
kafka.apache.org · 5 steps · unrated
Configure a Kafka Connect sink connector dead-letter queue with header reporting for failed record diagnosis
kafka.apache.org · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans