pingcap / pingcap/tidb-binlog

NATS sink

Open
#602 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request
Dominant language
Go
Stars
291
Forks
131
Avg merge
5m
Merged PRs (30d)
2

Description

I would like change events to be able to be published to NATS.
As I understand it Kafka is supported currently ?

NATS is written in golang.
NAtS and NATS Streaming are a different system btw. Only NATS streaming offers durable ACKS and should be the target.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by locating the existing Kafka sink and its configuration and acknowledgement handling, then determine how NATS Streaming would fit the change-event pipeline. Done means change events can be published to NATS Streaming with durable acknowledgements and the relevant behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
stream-processing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.