Configure and use Pulsar IO connectors (source and sink)

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

Steps

  1. Choose a Pulsar IO connector from the Pulsar IO catalog (e.g., Kafka source, JDBC sink, Elasticsearch sink); download the connector NAR file.
  2. Create a connector config YAML file with required options (connection URL, topic, database credentials via secrets).
  3. Deploy a source connector: pulsar-admin sources create --archive connector.nar --source-config-file config.yaml --name my-source --destination-topic-name output-topic.
  4. Deploy a sink connector: pulsar-admin sinks create --archive connector.nar --sink-config-file config.yaml --name my-sink --inputs input-topic.
  5. Monitor connector status with pulsar-admin sources status --name my-source or pulsar-admin sinks status.

Known gotchas

Related routes

Create and update a Pulsar IO source connector via pulsar-admin
pulsar.apache.org · 5 steps · unrated
Deploy a Kafka Connect source and sink connector
kafka.apache.org · 5 steps · unrated
Configure Apache Pulsar geo-replication at the namespace level and verify cross-cluster message delivery
pulsar.apache.org · 6 steps · unrated

Give your agent this knowledge — and 15,600+ 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